We have a tendency to answer questions of multi-tenancy in Tableau swiftly with switching between Sites, which are the virtual tenements for your Tableau tenants. But Sites are the simple part of the equation; when there is a need for multitenancy in Tableau, there is most likely existing multi-tenancy in the data systems Tableau must connect to. I’m going to dive into the diverse ways that customers corral their data and outline all the tenets of deploying effectively from a single template to all your tenants.
Tableau has a great whitepaper that explains all of the out of the box supported localization methods. But they are not exactly “seamless”; they take a lot of effort and still result in some quirks. In this post, I’ll explore how some simple modification to the Tableau XML files can provide a method to generate “fully” translated workbooks that are won’t look out of place even when using Web Edit or See Underlying Data.
To build a translatable workbook, follow these steps:
- Connect to your datasource. Do not rename any fields. Also do not create any calculations
- Publish the datasource to Tableau Server.
- Save the datasource as a .TDS file for later, in case you need to make changes.
- Connect to the published datasource on Tableau Server. Close the original local connection
- Save the workbook as a TWB
Now you have a workbook that is fully ready to be translated. Keep reading for how to make it work.