Export Excel not working with USERCULTURE() function !

[resuttano83]

Hello,

When exporting on excel a dax using userculture() in powerbi bi services the userculture does not work - it is still english-us.

It has big impact for all international companies.

The support say it is a "expected designed behavior". What a surprise : you see something on your analysis and export, the export is different, i would know who can be the "engineer" that created such a functionality 🙂 I hope that we have a misunderstanding with the support and that they should plan a correction as soon as possible 😞

Regards

[v-nuoc-msft]

Hi @resuttano83 

I understand that you have encountered difficulties using the USERCULTURE() function in exporting excel.

The userculture() function returns the user's locale, which is their preferred language and locale. This feature can be used to dynamically translate tabular data, visualization titles, and captions based on the user's culture.

However, this feature has some limitations and caveats:

It is only supported in Power BI Premium, Power BI Premium per User, and Power BI Embedded.

It does not apply to the dashboard’s theme, but only to the individual visualizations.

It may not return the correct user locale when used in expressions from outside the model, such as queries and live-connect report measures.

It may not work properly when exporting data to Excel, as Excel may use a different locale than Power BI.

Therefore, it is possible that the support team is correct in saying that this is an “expected designed behavior”, as the userculture() function is not intended to work consistently across all scenarios and platforms.

You might try the following:

Use the FORMAT function to explicitly specify the locale for each measure or column that you want to export.

Use the Power BI REST API to export data with the desired locale.

Use the XMLA endpoint to specify a custom locale for the dataset.

Regards,

Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[resuttano83]

We tried everything and there is no solution.

We saw the behaviour to ms team and they agreed that this is a problem.. but by design.. and officaly there are no workaround to change it without user impact....

Juste fy information we do not want one language but the dynamical langage of the user connected and we want users to do ad hoc analyses and to be autonomous, so no hardcoding or fixed dashboards...