Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Our current development process is to duplicate a sheet and work off the duplicated sheet while maintaining the public sheet. This allows a version control process that we can revert back to the original. We also have staff starting to use the subscription email functionality. We noticed that when we publish the updated duplicated sheet and archive their subscribed one the email subscription doesn't get updated. It'll error out because the sheet cannot be found. Is there any efficient way to manage either version control of sheets to maintain the subscription or quickly update subscriptions with the new sheet?
Hey,
I recommend adopting an organization based on two spaces: a development space (shared) and a production space (managed). The production space is reserved for the use of applications by end users, who only have access to this space. Developers, on the other hand, will work in the shared space, where they can modify sheets and make changes. Once the modifications are completed, the development application can replace the production application by publishing the development application and directing it to the production space. This system has the advantage of preserving subscriptions and updating sheets, as long as they are not deleted. Subscriptions remain unaffected because existing sheets are simply overwritten by the new versions.
Enjoy your Qlik.
Kind regards,
Théo ATRAGIE.
Hi @theoat ,
We do follow that design. However, in the shared space, we duplicate the sheet to maintain the original and then version it in our private sheet's space. This prevents the original from being messed up and a duplicate to have the new features.
How else would you revert to the original if the sheet isn't duplicated and you messed it up?
Hi,
In that case, you can create a duplicate to keep the previous version and make your developments on the original. This way, you preserve the previous version in Qlik while keeping the subscriptions. Alternatively, you can set up a GitHub backup when publishing an app. That way, your subscriptions remain intact, and if you ever need to revert to an earlier version, you can simply retrieve the QVF from GitHub!
Enjoy your Qlik.
Kind regards,
Théo ATRAGIE.
If app1 is in a development space, it has sheet1, which I want to modify, which is version 1. I accidentally deleted a chart, which has now become version 2. How would I undo the deleted chart and revert to version 1 if I edited the original sheet?