Here, everything suddenly looks upside down. The question why these two languages are missing in Power BI Desktop can be answered quickly by selecting one of the two languages in the Power BI service (here using Hebrew as an example): Power BI service with language Hebrew What is the difference? The Power BI service additionally contains the two languages Arabic and Hebrew. This list contains 44 languages, 2 more than the list in Power BI Desktop. If you go into the Power BI service, you can change the language of the UI there as follows: Switching languages in the Pwer BI service This list contains 42 different languages. When you save a Power BI Desktop file for the first time, the file remembers the initial model language (or default language), which you can determine as follows: Defining the default language of the model in Power BI Desktop Available languages – or: How to translate into Hebrew and Arabic Your data model must be in a premium workspace (premium per capacity or per user) otherwise your translations in Power BI Desktop won’t reach the service.īefore we look at how the whole thing works, a few words about the available languages.You need a version of Tabular Editor (2 or 3) and.To follow my solution path two requirements must be met: If you can afford it, buy it! Anyway: Because TE2 is free (download it here), I’ll show you how to do it with TE2. Daniel was then kind enough to point me to the macro recorder in Tabular Editor 3 to see how to create languages and do translations for the individual objects via C# script. In my attempt to find a solution for Excel-based translations, I asked Daniel Otykier – the creator of Tabular Editor – how it is possible to programmatically translate the objects of the data model via C#. In addition, there is an excellent article from the Tabular Editor team, from whom I learned a lot about how the process works manually. However, if you – like me – prefer editing in tabular form in an Excel file, then my current post should help you. There is already a well-documented solution to this problem by Kasper de Jonge, but it boils down to editing JSON files. You don’t have to create the individual languages (aka „cultures“) manually and then right click and rename each individual table, column and measure with a mouse click. But in this post I provide you with a practical solution that reduces your manual effort in Tabular Editor to a minimum after you have done the translation of the objects. You have to translate the names of tables, columns and measures yourself. To clear up any misunderstandings right at the beginning: No, my tool does not translate your data model by itself. In this article I will show you how you can significantly reduce the effort to translate your tables, columns and measure, while you can do the actual translation in tabular form in an Excel file. At the time of writing, the Power BI service supports 44 different languages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |