Best Practices - Moving DEV Dashboards to PROD
We have the following situation (using Sisense v.6.6):
-DEV platform - with a mix of dashboard designers and owners
-PROD platform - one owner (no development design here); aside from one admin/owner, all PROD users are viewers.
The time comes when (1) a new dashboard is to be moved DEV to PROD, or (2) a change is made on DEV to an existing PROD dashboard.
Is it necessary to transfer ownership to PROD owner before exporting from DEV? What is your best practice for organizing production-ready (i.e. released) dashboards on DEV? For example, do you move items to a release folder?
What is your best practice for managing publication? One consideration with (2) is that, on import, we want to be in position to OVERWRITE the existing dashboard.
We use the "Copy to Server" option to deploy our dashboards now. It is an awesome feature!
When I move to production, I am logged in as the administrator and that's who the owner is.
We do not have a "release" folder, we have one person promote to PROD, so the request is made and that person promotes the dashboard as it exists in DEV for the admin (in our case, DEV is actually TEST).
If your cube names and everything is the same, you can publish your dashboard automatically with the "Copy to Server" option. However, I prefer to push them all to PROD and then I go onto the PROD site to publish them. If I don't care if I overwrite user settings, I use the API (very fast). If I want to retain user settings or make a change like change the data set, then I do it through the "Republish" in the GUI. You can use the API for both, there is an option to force the update (true/false).
I hope this helps!3
Thanks.. I'll take a look at this.0
Please sign in to leave a comment.