Cultures and locales

Cultures in Power BI’s Tabular Object Model are identified by .NET culture codes like en-US, fr-FR, ja-JP, he-IL. Daxlate surfaces every culture in the Windows .NET globalization catalog (around 890 entries), so you can add anything from fr-CA to gsw-LI without juggling a hardcoded list.

What gets translated #

Each culture carries a translation set for two properties on every translatable object:

• Caption: the user-visible name (table, column, measure, hierarchy, hierarchy level)
• Description: the tooltip / metadata description

Hierarchies have an extra layer: each level inside a hierarchy is independently translatable, with its own caption and description.

DisplayFolder translations are part of the TOM model too, and Daxlate preserves them on round-trip, but folder editing is not exposed in the v1 grid. If your model already has translated folders, they survive a load / save cycle untouched.

linguisticMetadata #

The linguisticMetadata blob (synonyms and phrasings powering Q&A) is preserved on round-trip but not editable in the v1 grid. Editing happens in the model’s authoring tool; Daxlate round-trips the bytes intact.

Default culture #

The default culture is the one you pick when authoring the model. It’s typically en-US. Captions on the default culture are the source of truth. Any other culture missing a caption falls back to the default at report render time.

In the grid, the default culture’s column is shaded so you don’t translate into it by mistake. When you add a new culture, the Add culture dialog offers to seed it by copying from the default (or any existing culture) so you start with a populated baseline rather than blank cells.

RTL languages #

Cultures whose primary writing direction is right-to-left (Arabic, Hebrew, Persian, Urdu) are detected automatically. The grid cell flips its FlowDirection when you click into one, so what you type reads correctly. See Working with RTL languages for the details.