Going a bit further would be to use the OS system settings which is probably the most natural way for users to understand (write and read) numbers.
1 Like
Thank you @Bertrand_Bouteiller, @Breno_Nunes and @Stefan_Stoyanov for your feedback on better currency support.
1 Like
Hi, @Ayuba_Audu, besides the submit button, I would love to be able to customize the “blank” option inside a select or relation column in a table.
A better option would be to have a check box to disable the blank option as we have in the controls.
1 Like
@Stefan_Stoyanov—many thanks for the video, it was very helpful!
By default, number columns have their grouping separator on. This would mean in your video, the first column in the top left would show “7 400” in a new doc—watch my demo here in a new doc.
In your video, we noticed the grouping separator was off and why it displays as “7400”.
The behaviour you saw from switching is because currency always has the grouping separator on, so when you switched to currency it was turned on and carried over when you switched back to number.
You don’t need to do this to see the grouping separator. If it’s off, you can turn it on when you edit the column options.
If you’re seeing new docs you create with new tables have the grouping separator off, please let us know.
4 Likes
Thanks Christian, this is just it. @Ayuba_Audu, just today I had to use the trick someone shared on this forum of using the first row of a table with letters in columns that I wanted to be sure would remain as “text” and use a checkbox column to exclude that row from further calculations. Please, please let Doc Makers choose column types by themselves!
3 Likes
@Ayuba_Audu, concerning Forms, I just don’t understand why the “Submit” button can’t have the same option as the “New” button to add rows to tables: right click / button options / change label and voilà! Can you imagine having the “Submit” button of your forms in a foreign language for no reason? Neither can we 
4 Likes
I would really appreciate the ability to have number columns display differently depending on the view. For example, I have a table where one column shows a 6-digit number, while another column shows that same number formatted with k or M abbreviations (for thousands or millions). I have a similar issue with dates. I currently need 5 separate columns displaying the same date value in different formats to accommodate the requirements of various table and card views. This creates a naming challenge since I must consider how these column names will appear in table headers.
3 Likes
Thank you for taking the time to explain. Overlooked this option. No bug here 
2 Likes
@AJM—we’d love to dig into your scenario and see if there’s something we can do.
Mind sharing more details or doc with Coda support or me please at aaudu@coda.io?
2 Likes
Agreed.
I’ve shared this directly with the my team mates who look after this area.
1 Like
To confirm we’re following, is this about allowing you do something like this below—where all the options including “Blank” are in another language in this case Spanish?
Removing the “Blank” option could be tricky if you accidently select and decide to leave blank, since you’d have to select the column without focusing in, and hit the delete key.
1 Like
Appreciate the details @Bertrand_Bouteiller and @anon1959570!
1 Like
Thanks a lot! Now I’m looking forward to hearing from them! 
By the way, I just realized the Grouping separator option (which I had completely overlooked up until now, so thanks for that!) seems to be set to Off by default for Canvas formulas. And that’s why I was left wondering why my canvas formulas were not showing that nice brand new space separator 
→ Am I the only one thinking it would make more sense to have it set to On by default? Or at least to have an option allowing us to choose the default behavior? Region / Number is where I would look for that option if someone asked me…
1 Like
I don’t think that’s a problem. It should be up to the maker to decide if a blank option is needed.
Besides, this is exactly how it works with controls on canvas.
As you can see in the images bellow, I created an option “Em branco” in my native language, Portuguese.
In my humble opinion. it would add consistency. Why is this option only available on canvas? Why can’t I have it in a column.
ps. I know that there will always be a blank state, if you you focus and hit delete. A check box has also a blank state and it’s ok.
3 Likes
Hey @Ayuba_Audu, it’s me again, and sorry, I think I’ve just found a bug 
- or a least something else I wish worked differently
If you use numbers in a text formula (for instance using Concatenate), those numbers are displayed without grouping separator and with a dot no matter what. I wish there were a way to use the Regional Settings.
In the example below, my Regional Setting is set to “1 234,5” - and you can see that works well for a formula which gives a number as soon as I toggle the Grouping Separator on. But when I try to concatenate that number within a string, the formatting is lost.
4 Likes
And to be even more specific, I can get the behavior I want with an extra step.
- Use my first formula with
=12345/2 - Give it a name, for instance f_Number
- Reference that name in a second formula, for instance
=Concatenate("My number is: ",f_Number)
And as is often the case, what works with Concatenate doesn’t work with ="My number is" + f_Number.
1 Like
In one initial image you shared, there was a per doc global decimal setting. Are there plans to have this as a setting? Global settings tend to bring congruency within docs/apps.
1 Like
Hi @Ayuba_Audu , any follow-up to my comments?
I’d like to add that I’ve found an additional issue. Do you know what does break even my “Named Formula Workaround”? → Displaying the orginal number as “Slider”, “Progress” or “Scale”. Sure, I could use a third intermediate step to have 1/ my base number, 2/ my progress bar and 3/ my formula. But it doesn’t make much sense to me…
Here’s a screenshot of the issue both in canvas and table formulas:
Thanks in advance for your feedback!
And just to make things clear: it would help that the bugs on the number formatting in formulas got fixed, but they’re WAAAAAAAY less important / urgent that the issues with currency localization and Submit button that were also discussed in this thread. Please @Ayuba_Audu?