Ian Roberts on 04 Jan 2022 16:21:40
Established best practice for implementing multi-lingual reports at the data level (e.g. names of calendar months) is to have one row per language for this data in the appropriate tables, with a Language ID column to filter the results according to the desired language. Yet Power BI enforces a single row per date in the designated Date table for a data model. These two concepts are currently irreconcilable.
It should be possible to define multiple rows per date in the designated Date table, by introducing a mandatory and distinct Language ID against each row in that table. This would allow the use of Power BI's built-in time intelligence functions in conjunction with best practices regarding multilingual data.
- Comments (4)
RE: Multilingual Date Table
100%
RE: Multilingual Date Table
Same for my organization. it's a requirement for our client and it a law that our IT solution must be in French and English available for our users/customer.
RE: Multilingual Date Table
100%
RE: Multilingual Date Table
Very important in my organization because both English and French are official languages.