Creating Multilingual Reports with UI/UX Orientation Changes for Arabic Users

[ashi7upt]

Creating Multilingual Reports with UI/UX Orientation Changes for Arabic Users

We are building reports for Arabic-speaking users, with many of them using Arabic as their primary language. We are embedding these reports into an application using the "app-own-data" method.

Our goal is to create a multilingual report that automatically adjusts both the language and the UI/UX orientation based on the selected language. This includes changing the layout of tables and matrices. For example, if a table in English displays columns as "student_id," "student_name," and "marks," we would like it to display as "marks," "student_name," and "student_id" when viewed in Arabic, reflecting the right-to-left (RTL) reading orientation.

Is there a way to dynamically implement this in Power BI, where both the language and table layout change based on the user’s language selection?

[v-pnaroju-msft · Accepted solution]

Hi @ashi7upt,

We appreciate your query on the Microsoft Fabric Community Forum.

Power BI does not provide an in-built feature for dynamic mirroring of visual layouts (such as tables and matrices) based on language preferences. It is currently not possible to automatically adjust the order of columns in a table based on the language selection (e.g., Arabic or English). Furthermore, Power BI Desktop does not fully support right-to-left (RTL) layouts, which restricts our ability to directly configure such functionality within the .pbix file.

As a workaround, kindly follow the steps outlined below to address the issue:

1. Use the Translations Builder Tool to facilitate the management of translations and localisation for Power BI reports. It enables the creation of a single .pbix file that supports multiple languages, thereby eliminating the need for separate files for each language.

   For complete instructions, kindly refer to the following link:
   Create multiple-language reports with Translations Builder - Power BI | Microsoft Learn

2. Develop a Language table in the data model that enumerates all the supported languages and includes their corresponding translations for various report elements (e.g., titles, labels).
   Ensure that this table contains a column for language codes (e.g., "en" for English, "ar" for Arabic) and another column for the translated text.

3. Implement a Language slicer in the report that allows users to select their preferred language. Based on the user's selection, the displayed data will be filtered accordingly.
   Use DAX measures to dynamically retrieve the appropriate translations from the language table, depending on the selected language.

4. Modify the layout of tables and matrices to reflect the right-to-left reading orientation for languages such as Arabic. This may involve creating separate visuals that are specifically configured for RTL display.

5. Test your reports thoroughly by switching between the supported languages to ensure that all elements are correctly translated and the layouts adjust as expected.

For additional information and guidance, please refer to the following resource:
Building Multi-language Reports for Power BI in 2023 | Microsoft Power BI Blog | Microsoft Power BI

Should you find this response helpful, we kindly request you to mark it as the accepted solution and provide kudos. This will greatly assist other community members facing similar queries.

Thank you.

[v-pnaroju-msft]

Hi ashi7upt,

We are following up to see if your query has been resolved. Should you have identified a solution, we kindly request you to share it with the community to assist others facing similar issues.

If our response was helpful, please mark it as the accepted solution and provide kudos, as this helps the broader community.

Thank you.

[v-pnaroju-msft]

Hi ashi7upt,

We wanted to check in regarding your query, as we have not heard back from you. If you have resolved the issue, sharing the solution with the community would be greatly appreciated and could help others encountering similar challenges.

If you found our response useful, kindly mark it as the accepted solution and provide kudos to guide other members.

Thank you.

[v-pnaroju-msft]

Thank you @SaiTejaTalasila for the response.

Hi ashi7upt,

We have not received a response from you regarding the query and were following up to check if you have found a resolution. If you have identified a solution, we kindly request you to share it with the community, as it may be helpful to others facing a similar issue.

If you find the response helpful, please mark it as the accepted solution and provide kudos, as this will help other members with similar queries.

Thank you.

[SaiTejaTalasila · Accepted solution]

Hi @ashi7upt ,

You can refer this article-

https://data-marc.com/2023/01/09/how-to-make-your-power-bi-solution-support-multiple-languages/

You can try this -

To implement multilingual reports with dynamic field parameters, enable Field Parameters in Power BI and create a parameter (e.g., "DynamicColumns") that includes fields for both English and Arabic layouts, reflecting their respective column orders. Add a Language Table with options like "English" and "Arabic," and create a slicer for users to select their preferred language. Use DAX logic (e.g., SELECTEDVALUE) to filter the parameter values dynamically based on the selected language, ensuring the visual switches between layouts automatically. Adjust text alignment (LTR/RTL) in the visuals for proper orientation using formatting options.

https://youtu.be/nAypPLYbeb4?si=F3qyiKUtJORzfw06

I hope it will be helpful.

Thanks,

Sai Teja 

[v-pnaroju-msft · Accepted solution]

Hi @ashi7upt,

We appreciate your query on the Microsoft Fabric Community Forum.

Power BI does not provide an in-built feature for dynamic mirroring of visual layouts (such as tables and matrices) based on language preferences. It is currently not possible to automatically adjust the order of columns in a table based on the language selection (e.g., Arabic or English). Furthermore, Power BI Desktop does not fully support right-to-left (RTL) layouts, which restricts our ability to directly configure such functionality within the .pbix file.

As a workaround, kindly follow the steps outlined below to address the issue:

1. Use the Translations Builder Tool to facilitate the management of translations and localisation for Power BI reports. It enables the creation of a single .pbix file that supports multiple languages, thereby eliminating the need for separate files for each language.

   For complete instructions, kindly refer to the following link:
   Create multiple-language reports with Translations Builder - Power BI | Microsoft Learn

2. Develop a Language table in the data model that enumerates all the supported languages and includes their corresponding translations for various report elements (e.g., titles, labels).
   Ensure that this table contains a column for language codes (e.g., "en" for English, "ar" for Arabic) and another column for the translated text.

3. Implement a Language slicer in the report that allows users to select their preferred language. Based on the user's selection, the displayed data will be filtered accordingly.
   Use DAX measures to dynamically retrieve the appropriate translations from the language table, depending on the selected language.

4. Modify the layout of tables and matrices to reflect the right-to-left reading orientation for languages such as Arabic. This may involve creating separate visuals that are specifically configured for RTL display.

5. Test your reports thoroughly by switching between the supported languages to ensure that all elements are correctly translated and the layouts adjust as expected.

For additional information and guidance, please refer to the following resource:
Building Multi-language Reports for Power BI in 2023 | Microsoft Power BI Blog | Microsoft Power BI

Should you find this response helpful, we kindly request you to mark it as the accepted solution and provide kudos. This will greatly assist other community members facing similar queries.

Thank you.