Forum Discussion
Multilanguage Field Parameter
- 7 months ago
Hi iceparrot,
You will need to set up your parameter table to include the culture as well as the equivalent of the field for that culture.
// Parameter table with culture Parameter = { // Culture: en-US ("Album", NAMEOF('Data'[album]), 0, "en-US"), ("Artist", NAMEOF('Data'[artist]), 1, "en-US"), ("Explicit", NAMEOF('Data'[explicit_text]), 2, "en-US"), ("Genre", NAMEOF('Data'[genre]), 3, "en-US"), ("Track Name", NAMEOF('Data'[track_name]), 4, "en-US"), ("Track ID", NAMEOF('Data'[track_id]), 5, "en-US"), // Culture: de-DE ("Album", NAMEOF('Data'[album]), 0, "de-DE"), ("Künstler", NAMEOF('Data'[artist]), 1, "de-DE"), ("Explizit", NAMEOF('Data'[explicit_text]), 2, "de-DE"), ("Genre", NAMEOF('Data'[genre]), 3, "de-DE"), ("Titel", NAMEOF('Data'[track_name]), 4, "de-DE"), ("Track-ID", NAMEOF('Data'[track_id]), 5, "de-DE"), // Culture: fr-FR ("Album", NAMEOF('Data'[album]), 0, "fr-FR"), ("Artiste", NAMEOF('Data'[artist]), 1, "fr-FR"), ("Explicite", NAMEOF('Data'[explicit_text]), 2, "fr-FR"), ("Genre", NAMEOF('Data'[genre]), 3, "fr-FR"), ("Nom de Piste", NAMEOF('Data'[track_name]), 4, "fr-FR"), ("ID Piste", NAMEOF('Data'[track_id]), 5, "fr-FR") }It is possible to automatically filter a slicer with a measure to the culture relevant to the user, but not if the field parameters are used in other visuals. Using the measure below will not filter the visible columns but will instead hide all rows:
culture_check = IF ( SELECTEDVALUE ( Parameter[Culture] ) = USERCULTURE (), 1 )
Field parameters don’t support dynamic labels via DAX (so USERCULTURE() can’t rename "Placement", "Clicks", etc.). The display names in a field parameter are static.
The practical workaround is to create separate field parameters per language and show the right one based on language.
Example:
kpi_tabelle_EN (Placement, Impressions, …)
kpi_tabelle_DE (Platzierung, Impressionen, …)
Then either:
Use a bookmark toggle (EN/DE) to show the correct slicer + table, or
Use a language table + field parameter selector pattern (two visuals, one per language), and hide/show based on language.
If you want the cleanest setup with minimal duplication: use two slicers (EN/DE) + two tables and control visibility with bookmarks. That’s the most reliable way today.