Launched: More Currency format options & Format formulas

More currency formats options

Many of you have shared feedback on wanting more flexibility with currency formatting & currency defaults in Coda.

Today, we’re happy to share new and updated:

  • Column & doc currency format settings that allow you to choose how currencies—position & symbol—are best displayed in your docs. This setting can be applied to a specific column or your current doc.

  • Default account currency format settings that apply to all new docs you create.

Either way, once you configure a setting, you can have it apply to new or existing content—read more in our help article.

3 new formatting formulas

We also have 3 new formulas that allow you format values like a currency, to give you even more flexibility:

  • FormatCurrency() → Display currencies with the right symbols and separators. Whether you’re tracking budgets in dollars, euros, yen and so on.

  • FormatNumber() → Control exactly how numbers appear in your doc by adding grouping separators or setting decimal places.

  • FormatPercent() → Convert decimals into clean percentages that make sense at a glance. 0.85 becomes 85% which perfect for progress tracking, growth metrics, and completion rates.

You can read more about each of these formulas in our formula reference.

Many thanks again to everyone who’s shared feedback and their use cases!

27 Likes

How about more international official currency symbols? (ehem ₱)… even Bitcoin has just been supported :frowning: or how about as general as custom symbol :neutral_face:

(PS: Notion supports “more” currency symbols, (supported even years ago)… just saying)

1 Like

Thanks for your feedback, @chrisquim! FYI—we have had Bitcoin in the product for sometime.

image

I’d love to know what currency symbols you would like to see and are blocked by?

1 Like

Mauritius Rupees, please!
’Rs.’

1 Like

“I’d love to know what currency symbols you would like to see and are blocked by?”

@Ayuba_Audu1 This is really straightforward to test. I just went through the list on xe.com or wikipedia and quickly found a huge number that aren’t supported.

I just can’t understand why you wouldn’t use a complete list of ISO 4217 currency codes like that which is available from xe? It seems like it would be even more work to go through the process of cherry-picking the codes (i.e. countries) to include as you have done, rather than just bulk apply them all.

Or for that matter, why not just allow the user to enter any text as their chosen “currency code”?
Let the user freely add any text or unicode character/s to use as a “currency” symbol. I don’t know what the use case would be, but I wouldn’t be surprised if someone would have a use case for it (perhaps some business marketing simulation ‘game’ like those in education or some kind of internal accounting-esque feature inside a company??) where currency-formatting rules are needed but to apply to some fictional “currency”.
Why not even let the user decide to use an emoji if that’s what they want to do - why not?

Why is Coda not simply agnostic to the currency codes a user wants to use, rather than making (non-transparent to users) value judgements about which countries’ currency codes it chooses to implement and which it doesn’t?

So, if a user enters a 3 digit code that corresponds to any one of the codes in the complete ISO 4217 list, then that is used, but for all other values, just simply use whatever text value the user enters.

8 Likes

Please add the currency “MDL — Moldovan leu”:

ISO codes 421 — MDL (498)
Symbols — L
Abbreviations — L

1 Like

as for “cherry-picking"… I would badly beg ask for Philippine Peso please ₱ (PHP) :pleading_face::folded_hands:t4::folded_hands:t4::folded_hands:t4:

This is well supported from the start in Notion.

Bitcoin symbol support in coda what just added recently.

1 Like

:raising_hands:t4: much needed and finally here, thanks for adding this. Saves a lot of time now ..

2 Likes

Nice to see those functions advancing from hidden to official ones :slight_smile: Now there’s only FormatDateTime() left :wink:

+1 the request to support arbitrary currencies or even arbitrary symbols (i.e. so that I could just type in FormatCurrency("₱", 123) like the docs actually say (nowhere they say it must be a symbol from a defined enum list):

7 Likes

Thanks @Ayuba_Audu, we’re getting there!

But we’re not quite there yet :rofl:

Thing is, in most European countries, we use a non-breaking space between the number and the € symbol. I can get that with FormatCurrency(“€”,123456.78,“accounting”,2,“after”) but:

  1. This should definitely be a regional setting that we can change at Doc / Workspace level. I want my spacing to be correct without having to use a workaround. We can now change the default position and I greatly appreciate the improvement, but there’s no reason why we shouldn’t be able to choose the default spacing as well.
  2. Yeah, I used the term “spacing”. In my opinion, using “format” in the formula with the options “currency”, “accounting” or “financial” to actually determine the spacing or lack of symbol is just plain wrong. “Spacing” should be a binary (with or without spacing). If you want to talk about “format”, you could argue that a format is a combination of symbol + position + spacing + thousand separator + decimal separator, but that’s it and honestly, I don’t really see the point. Furthermore, you already used the term “format” in the settings to convey the various thousand separator and decimal separator options. Using it now for a completely different purpose is just misleading.

I really, really hope you can apply those changes quickly!

2 Likes

@Ayuba_Audu Appreciate the efforts! Listen to Paul!

Seriously - hire him as advisor to give you more complete solutions for most of your UX problems.

3 Likes

Hi Ayuba, this is a step in the good direction.

Coda is a great tool and I love developing solutions for my team with it.
However, up until now, Coda’s UI has remained very Anglo centric.
I work in a multi-lingual context and it would be awesome to have a feature that allows users to select the language of their preference. If we had the opportunity to define the document languages when a page is created (one main and additional languages), then this could pop up as selectable fields, for example, when a column is created, you can select one language, enter the name of the column, select the other available language, enter the name of the column in that other language, etc. Same with buttons, tables, and all other objects we tend to put in pages. For formulas, only the main language would be used for object references.

That would bring Coda to another level and make life easier for makers like me, from Canada, and those from Europe that need to develop tools in multiple languages. If localization is not in Coda’s roadmap, please be transparent about it. It may be a breaking point for some of us but we won’t spend time developing tools that have no chance of evolving or trying to find impossible workarounds; we might need to turn to other solutions.

Thanks. I remain hopeful.

1 Like

@Ayuba_Audu Beat me but for a while I ceased to try to understand Coda product development. Before we had “kr“ as danish kroner… now there is only “Norvegian Kroner“. Why… god knows why this change.

3 Likes

A small step for Coda, but a giant leap for the rest of humanity. We were so looking forward to this… Thank you so much!

3 Likes

OK @Ayuba_Audu it’s actually even worse than I initially thought. So sorry, I know my name isn’t Pete, but I’ll keep on rambling anyways :wink: I’m really frustrated because I’m confident that with the amount of work that the team put into that update, it could’ve been right, but it still isn’t. Which means currency formatting is still unusable in France - and in many other countries. Let’s break it down.

When I said that I could achieve what I want / need with FormatCurrency(“€”,123456.78,“accounting”,2,“after”), it turns out that I was wrong! I only quickly tested it in a canvas formula and yeah, it does display 12 3456,78 €, which is what I’m looking for but… it’s not the case in a column formula! So since it’s not properly documented anywhere yet, let’s have a look at how the three different “formats” work:

  • Currency displays numbers aligned on the right with their symbol next to them and negative numbers with a minus sign,
  • Accounting displays numbers aligned on the left with their symbol aligned on the right and negative numbers between brackets,
  • Financial displays numbers aligned on the right without any symbol for some reason and negative numbers between brackets.

There are two fundamental flaws here:

  1. You use the word “Format” which is very vague (it’s like “Type”, it should be prohibited when we need to be precise), and that actually translates into aligning things AND BYPASSING OTHER SETTINGS. It’s not a setting per se, it’s just a mix of other settings. If you choose “Financial”, it doesn’t matter what symbol you choose or whether you want to display it after or before the number: it won’t be displayed!
  2. THERE IS NO WAY TO CUSTOMIZE SPACING

I’m getting a little bit upset here, but wherever you look (for instance here or here), you’ll see that currency format localization mainly translates into the following settings:

  1. Symbol
  2. Thousands separator
  3. Decimal separator
  4. Placement (symbol diplayed before or after number)
  5. Spacing (is there a space between the symbol and the number or not)

So the situation after the last update is better than before since we now have a way to properly customize settings 2, 3 and 4 and even use default settings in our Docs. And once again, I’m grateful for that. But there are still two things missing:

  • As others have already pointed out, we should be able to freely choose the Symbol we want to use. It’s not your job to maintain a list of “Coda-curated currency symbols”, so you should just let got. And actually, this would also help in an unexpected way because that would also allow us to natively manipuate other units like kilograms or square meters! Just by letting go of a list which is incorrect anyway! How great is that?
  • Just implement spacing and allow us to use a default setting for our Docs and Workspaces. Please. As simple as that.

As for the “format” input in the FormatCurrency formula, you might have noticed I’m not the biggest fan. My advice would be to drop it altogether, and replace it with two additional settings that I didn’t mention above because of the “mainly” phrasing (I’m sure they would be useful for some cases, but way less important than “symbol” and “spacing” to reach proper localization):

  • Negative numbers → “minus sign” or “brackets”
  • Alignment → Left or right

And there you go! With those (relatively) simple changes, you now have a proper localization of currencies AND you make Makers happy because they can also work natively with other units. I really, really hope you’ll listen to us on that one.

7 Likes