

Tableau adoption happens at a different pace for every company. Some Tableau deployments take off like wildfire while others plod along, inching forward slowly but gaining momentum with the inevitability of a glacier.

If you are a Tableau champion, adoption throughout your organization is a wonderful image to behold as your new users display child-like joy as they discover the secrets of their own data. But as with all things, growth comes with challenges, and the growth of Tableau in an organization is no different.

Ensuring data quality


In order to ensure data quality, QA processes will be born. Those QA processes will be multi-stepped and most likely require multiple environments to support them. However, one of the challenges to having multiple Tableau environments is that you then have to migrate Tableau workbooks and published data sources from one environment to another.



Common names for these environments are development, test/QA, staging/pre-production, and production. There are typically three to four environments (staging/pre-production is often omitted). These environments can exist as either separate projects or as sites on the same Tableau Server instance. Or each one might be a separate instance of Tableau Server.

QA process

The QA process is straightforward when we look at it from a high level. Below is a simplification of the workflow. Realistically you will have a back-and-forth between the QA analyst and developer as issues are found.

  • Developer creates workbook or data source
  • Developer tests workbook or data source for correctness
  • Developer tests workbook or data source in development environment
  • Developer pushes to test environment of Tableau Server
  • QA analyst tests workbook or data source in test environment
  • Release manager pushes to production environment
  • Release manager does final testing on production environment

How do I move all the things?


Migration options


Tabcmd Script
Enterprise Deployment Tool by InterWorks





Tableau REST API








Enterprise deployment tool by InterWorks




What’s the right decision?




Você também pode gostar de...


Has anyone had a deployment test script that you can share?

Will this API work if the datasource is Teradata?

Hi, we need to refresh our non-production from production every week and disable all subscriptions/refreshes in non-production(entire process needs to be automated). what is the best way of doing it? I'd appreciate any help in this regard


Has anyone created a live datasource [tds] from programming? I need to have connection to either SQL Serever, MySQL or Mongo DB?

Any reference will be much appreciated.

Thank you


Why DFSR is still the best option: If you want to copy files with same set of permissions (same hash) and it should replicate files with latest changes.

TabMigrate is a lifesaver for me! When I was on leave, my manager asked someone to install a Tableau server. When I returned, I have in my hands a multi-site server that has Production Site, Dev Site, Staging Site, and Testing Site. It took 4 months to convince management that this is not the ideal deployment and another Tableau server was provided. Now, I have two separate Servers: Production and Test servers. I wish I had the Tableau Powertools from Interworks but management will not buy anything! TabMigrate helped me sort through the chaos of migration. Each Server now only has two sites: Private and Public.

Assine nosso blog