I'm wondering if there are recommended practices for moving flows and their dependents (data sources and workbooks) ?
Our organization had a very structured process: creators can publish in their DEV folders, but Admins are required to move it out of DEV into PROD.
Previously our team used SQL exclusively to pull data for their workbooks, so migrating from DEV to PROD only meant overwriting the single file.
We are expanding to Prep, however this seems to come with some complications:
When we move from DEV to PROD at several steps are needed:
- Output generated by the flow must be redirected to to DATA SOURCES, rather than the DEV environment... so the flow must be edited.
- The flow must be moved out of DEV and into the PROD environment (our FLOW directory).
- The OUTPUT in DEV must be moved to DATA SOURCES. Luckily, this move cascades with any dashboard connected to it: those workbooks do not need to be edited.
- Lastly, the workbook(s) in DEV must be published over older workbook(s) in PROD.
Are these the steps others have used, or can you provide advice to reduce the moving parts?
Michael Hesser (Tableau Forum Ambassador)
@Michael Hesser
Hi, I guess you see the problem lot of people has when moving flows from one environment to other environment. I don't know a solution for this. The only thing I remember was Chris Perry a Data Dev hackaton winner, who built an app for restoring flows (https://devpost.com/software/flow-restore-utility) but he has not made the code available. So, it is a little bit sad.
Maybe, you can convince him about making the code public or get in contact with him.
If this post resolves the question, would you be so kind to "Select as Best"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.
Regards,
Diego Martinez
Tableau Visionary and Forums Ambassador
