Hello, I have a development and a production on-site instance of Sense. We develop changes to applications in dev, using test data or a small subset of data, and want to promote to prod with users seeing only production data. In QlikView, this was not a problem because there were separate source and published instances of each app. But there is no such distinction in Sense, and the user sees whatever app was published there, along with any data that it contains.
How do I promote app updates in such a way that the end user does not see the changes until the app has been reloaded in production? I am aware that I can export without data, but that comes with the same problem--until reloaded, users will see the app as empty. Reloading with full data in Dev before promoting is not practical, due to the volume of data and for other reasons. Preferably, I would like to promote the apps without involving any add-on products or third-party tools. Has anyone solved this problem? Thanks.
I don't think you can do that. You will have to reload the application at some point, on dev or prod (you can reload in Prod with Prod data prior to Publish it). Can you please tell in detail what is your promotion process?
I don't think you can do that. You will have to reload the application at some point, on dev or prod (you can reload in Prod with Prod data prior to Publish it). Can you please tell in detail what is your promotion process?
Mark, we are newly migrating to Sense from QlikView, so there isn't a promotion process yet; that is what I am designing now. I had hoped to do it like this:
Developer tests changes in dev environment, usually using a recent subset of prod data
Admin exports app without data
Admin checks empty app into source control--not for automated deployment, only for traceability and in case a rollback is needed
New apps: admin uploads app to prod, reloads and publishes--no problem
Existing apps: admin uploads app to prod, and somehow reloads with full data before the updated version becomes visible to users.
I think we can upload the updated app as a new app with the same name, and reload before overwriting the old version, but this sounds very messy and easy to make a mistake. And since some of our apps take hours to reload, it would become nearly impossible to complete promotions in a single business day if we have to reload as part of the process. Unfortunately it seems like another useful feature of QlikView that didn't survive the jump to Sense.
