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.
5 Comments
- Javed_AsifNew Member
Very important in my organization because both English and French are official languages.
- Al-Braich_HasanNew Member
100%
- fbcideas_migusrNew Member
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.
- Ashish_ChhattanNew Member
100%
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
OneLake Catalog full-text and content search
Why is it not possible to search OneLake by item description or even content? So I was thinking about how a user can find a table if they don't know in which lakehouse it is located? Why can't you se...TePe13 hours agoHelper IVPlanned1.1KViews21likes5Comments