I have a 'master app' that I’d like to distribute to multiple managed spaces in the Qlik Sense Cloud once I have made changes in the master app (in the script or in any object). The only difference between all those copies should be the output of a variable called vClient (containing the name of the respective client) and a button that executes an automation which in turn reloads the respective app. I only want to distribute the qvf, not the loaded data.
I am aware of the automation template called 'Distribute measures from one app to all apps in a space', which is further explained in the following article: https://community.qlik.com/t5/Official-Support-Articles/Distribution-of-measures-to-multiple-Qlik-Se.... However, I was wondering if there is an easier solution to this that maybe some you experts already came up with? I am not that familiar with the automation blocks and how to combine them. I'd appreciate any idea. Many thanks in advance.
many thanks for the hint. In the meantime, I came up with a solution myself. I developed an automation that creates a copy of the master app for each user, whereby each copy gets a customized name. A second automation using the "Publishing App to Managed Space" block then publishes the apps to the respective managed spaces. By using the '(Re)publish by name' as the run mode in that block I can opt for only publishing the app w/o data, so each individual button keeps the connection to the respective automation triggering the reload.
With GetSysAttr you can get the current space name. With that you might be able to change the URL or datasource with If statements so you dont have to make manual changes before a publish.
many thanks for the hint. In the meantime, I came up with a solution myself. I developed an automation that creates a copy of the master app for each user, whereby each copy gets a customized name. A second automation using the "Publishing App to Managed Space" block then publishes the apps to the respective managed spaces. By using the '(Re)publish by name' as the run mode in that block I can opt for only publishing the app w/o data, so each individual button keeps the connection to the respective automation triggering the reload.
