We migrate workbooks across three environments, development, test, and production.
We do it the old fashioned way. We copy each workbook and the extracts from dev to test and then publish on test
after testing we again copy each workbook and extract from test to production and then publish on production.
We use the same server site and setup different projects. For example, ProjA and ProjAtest. Desktop users publish wrokbooks to ProjAtest and then when approved, they are moved to ProjA.
How do you copy each workbook? Is there a way in the backend? I don't see that option in the frontend. Or do you download the workbook and re-publish to the test or production environment?
The most important thing is that I review the workbook and make sure it gets a new path. I think there are two options:
views/client_test/dashboard1 should become views/client/dashboard1
/t/test/views/advertiser/dashboard1 should become views/client/dashboard1
We don't access the workbooks via the normal Tableau login, but via Trusted authentication. If you know a way to move workbooks and give a new path, that would be very helpful!
I just use windows file copy to move files between servers. I have a folder for Workbooks and a folder for extracts.
There isn't anything on the frontend or backend for migration of workbooks.
Hi Mark, this sounds ideal. How can you configure the folder that you are publishing your workbook to?
Where is it located on the tableau server directory? I can't find the corresponding folder for some reason on our server...
Bumping up for an answer.
I think you're misunderstanding Mark's reply. You actually can not move workbooks or extracts from one site to another (or from one server to another) just by copying the files. You have to download the file from the original site (or server) and then re-publish to the new site (or server). Tableau keeps a lot of metadata about the workbooks in the repository database. That database only gets updated if you use the regular publish commands (either via the web GUI or the tabcmd commands). If you just copy the files, Tableau Server won't have any idea that they exist.
We use a third-part tool called Kintana for lifecycle management. The tool can run the command line "tabcmd" syntax to export the workbooks from one site (or server), check into version control, copy to another server if needed, and then publish to the required destination.
Gotcha. Mark's final reply was poorly worded then. The whole download/upload process is what we're doing and that makes sense to what you're saying, Benjamin.
We are looking forward to similar approach. We are able to move a file with its a datasource and extract coupled in it.
However, we faced some issues in moving dashboard with published data source from test server to production server. Does it work?