Tabular Editor lets you export translations into the same .json file format used by Visual Studio and SSAS Tabular Translator. This is useful if you want to delegate the task of translating your model to someone without access to your tabular model metadata. Let’s say you’ve added a new culture (called “translation” within Tabular Editor) to your model, and exported it to .json, without having translated anything yet within Tabular Editor:
The .json file will have the following structure:
The first section (“referenceCulture”), specifies the physical names of all translatable objects within the tabular object model tree. The second section (“cultures”), holds a single object representing the translation that we exported through the UI. Unfortunately, as you can see on the screenshot above, this object does not hold anything other than the name of the culture (in this case, “da-DK”). The person who’s going to supply the translations, will have a hard time figuring out what to do with this file, since there’s no obvious place to enter the translated names. They would have to know about the json schema of these translation files, and fill out everything accordingly – quite a daunting task.
To provide a file that is easier to work with, let’s use Tabular Editor’s Advanced Scripting functionality, to apply a default translation to all objects that are not yet translated. Simply execute the following script, before exporting the translation: