Internationalization support for numbers and currency in embedded dashboards

Hi QuickSight community,

I’m building an embedded analytics solution for a global audience and I’m struggling to find a clean way to handle internationalization — specifically around currency symbols, decimal/thousand separators, and locale settings. I’m hoping someone has found a better approach than what I’ve come across so far.

What I’m trying to achieve

There are three related scenarios I need to cover:

1. Dynamic currency symbols driven by data or parameters I need the currency symbol displayed to reflect the actual currency in the dataset or a parameter — ideally without hardcoding it in the analysis.

2. Dynamic decimal and thousand separators Different regions use different conventions (e.g., 1.000,00 vs 1,000.00). Is there a way to adapt these to the viewer’s locale at runtime when embedding?

3. Setting language/locale at embed time Is there a locale or language option available in GenerateEmbedUrlForAnonymousUser, GenerateEmbedUrlForRegisteredUser, or the JavaScript embedding SDK contentOptions that I may have missed?

The parameter + calculated field workaround (concatenating a symbol or separator as a string) does work to some extent, but it converts the field to a text type — which means losing numeric aggregation, sorting, and compatibility with visual types that require numeric fields. That’s a significant trade-off for a production dashboard.

My question

Is there a supported way to handle locale-aware number and currency formatting in embedded dashboards that keeps fields as numeric types? Or is the string concatenation workaround currently the only option?


Thanks in advance!

Hi @kilian.mueller,
Thank you for bringing this question to attention; overall, there is not a clean easy way to set this up dynamically, since the formatting happens at the authoring level and you are unable to set dynamic value formatting on a visual unfortunately.
For that aspect, I’ll tag this as a feature request, dynamic formatting of values would be a great addition!
Thinking in terms of another idea for a work around, this may call for additional setup, maybe this could potentially work. My thoughts would be to publish the dashboard in each respective language, then when embedding, you call the proper dashboard id based on the preferred language of that user.
Let me know if something along those lines may work for your case!