The Unique ID field is great, and being able to add a prefix and also program a set of leading zeroes is super helpful. I have a field in an app with this level of formatting and it displays great.
However, when I use this field in another calculation field, all it shows is the numerical unique id without any of the formatting. Is there any way to create a Unique ID field and then show the exact same formatted unique ID elsewhere via calculations?
I just wanted to give this a bump and also add something. It seems that when the Unique ID is the top field in an app, when viewing the records in a relationship field, it just shows as Untitled and doesn’t show the formatted ID.
Hi @andrew.cranston,
Many thanks for reporting these two issues.
The problem where the title reverts to “Untitled” if a Unique ID field is set as the first field was very likely caused by our recent title refactor. We will fix this and let you know once the fix is live.
Regarding the Unique ID currently being displayed in a Calculation field only numerically and without the prefix – this is intentional and aligns with how it is handled in Podio. The advantage is that mathematical operations can be performed more easily, and the prefix can be added manually within the Calculation field if needed.
However it would indeed be a valuable addition to offer a token for the formatted ID as well. I’d be happy to convert this issue into a feature request afterward. I believe the effort required should be manageable, so it might find its way onto the roadmap soon.
Best regards,
Leo
Thanks for bringing this up @andrew.cranston - there was indeed an issue when unique ID fields were used as title. The team was able to resolve this quickly - could you confirm on your end that it’s now behaving as expected? 
Cheers
Tim
@Tim Yes I can confirm that the issue is fixed now, thank you!
@Leo And yes, I’d love to convert this to a feature requests where the Unique ID can appear in other calculation fields in its formatted value. I’m using automations now to pop the value into a Single Text field but it would be much more efficient without this workaround.
Thanks so much to you both!