Many of you have shared feedback on wanting more flexibility in your number formats, in particular, on which decimal and grouping separators are used in your docs.
Today, we’re happy to share a new doc-wide, number format setting that allows you to choose how numbers are best displayed for your docs.
This setting can be applied to your current doc, or you can navigate to the account settings to apply it to all new docs you create. Either way, once you configure a setting, it will apply to all new and existing canvas formulas and tables—read our help article for more details.
For future updates, we’re considering how to better support international team scenarios where team members are distributed across the world, and preferences for format are varied, likely via a personal setting. We’ll share updates as we have them.
Many thanks again to everyone who’s shared related feedback and their use cases.
FINALLY!!! Many thanks @Ayuba_Audu and whoever else worked on that update! I haven’t tested all scenarios yet (especially imports) but that looks promising.
HOWEVER, we’re still missing the option to position the currency symbol after the number and not before… As stated many times here and there, the correct way to display currencies in the EU is for instance 1 234,50 € (notice the non-breaking space between the number and the symbol). Currently we can only get €1 234,50 which is still better than the €1,234.50 that we used to get, but still not quite there yet. I’d really like to drop all the regex shenanigans and I’m sure you can make it happen!
On a side note, I saw in another thread that you seem to be working on the “change text column to number column when we auto-detect that we think that’s what you should have done” feature/bug → that would also immensly help international teams (amongst others).
One last thing that would help international teams tremendously and would require (I think) very little effort on your part is the ability to customize the “Submit” button in Forms. Honestly, I can’t overstate how stupid you look when a client tells you “yeah yeah, you tell me your Coda tool is great and all, but you can’t even format numbers properly and you can’t customize the Submit button on Forms? Thanks but no thanks”. It looks like we’re getting there on the first half: let’s make the other half happen too!
I agree with your clients. It’s stupid. That’s why I use Tally forms together with webhook automation (not the tally pack).
It’s definitely something they need to get fixed.
What great news finally! So many years waiting for this small but significant change. Thank you so much.
There are still some related issues that don’t work:
If I paste numbers in this new format, it doesn’t recognize them as numbers; instead, the column is set to text. Then, if I change it to number, it recognizes them correctly, but doesn’t do so automatically.
Currency format:
If I paste numbers in currency or accounting format (in Europe, € is used at the end, not the beginning), it isn’t recognized, so I have to manually edit each number and delete the symbol for it to recognize it as a number or currency.
Likewise, the accepted format, once corrected, is with € at the beginning, which isn’t normal in Europe.
The default currency format is always $. Ideally, it can be changed to the user’s currency by default, so I don’t have to change it every time.
“More” is very important word in this announcement. Like others pointed the currency formats exclude pretty much 4/5 of the world’s localization standards - currency symbol at the back (with and without non-breaking space), currency symbol infront with non-breaking space and 3-letter ISO (with and without non-breaking space):
$ 1,234.56
USD 1,234.56
1 234,56 €
1 234,56 EUR (used in almost all important financial documents KIID, AR, SAR, etc.)
Number formats also lacking a couple, most notable:
123 456.78
123456.78
@Ayuba_Audu
Seems like a bug - when switching to xxx xxx,xx it did not add the spacing for the thousand separator. It changed the numbers only after manually updating the column format (e.g. switching to currency and then back to number) - 22.07.2025_17.54.56_REC
Edit: Not a bug as Ayuba explained below. It’s a toggle Grouping separator which overrules the doc numbering settings on column level.
What is crazy is that these UI request such as having the damn currency symbol behind… aren’t impacting anything related to the CFL. Like what is holding the team from iterating an UI for this? For me is just lack of interest from Coda. I keep seeing silly “features” being requested for years and NOTHING.
We have a few follow up questions to make sure we understand.
Is there recent example while using Coda where this would have helped?
We’d love to hear what customisation would have helped you recently? For example, changing the word “Submit”, or the position on the form, something else?
@Breno_Nunes—please feel free to share your examples as well.
Ayuba, this is a thing that was mentioned many, many, many, many times. We have an empty table with text columns, then the user inserts a number by mistake or not (zip codes that contain letters/numbers) and Coda will chnage the text field to a number… and break many things down the road like automations or a pack formula that expects a string rather than a number etc.
Like if I as a maker or even an editor wanted a column to be text… leave it as text.
)