Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I was looking for a way to enable us to build a template app that contains some sheets which our users can use as a standard template of visualization objects (e.g. bar chart, line chart, etc.) and can copy the object into their sheet. But we don't want users can edit these templates since this could destroy the templates. We were thinking about giving the users access to just duplicate the sheet or copy the objects from the template sheet without allowing them to edit the app or the sheet. Is it possible to do so? Or do you have any better way to achieve it? FYI: we use Qlik Sense Enterprise and Vizlib.
Thanks in advance.
You don't need a specific rule for this. Any user with a Professional license should be able to duplicate sheets by default.
For us, users usually just create a sheet based on the template and work with that. However, if you want them to be able to use the template to add objects to existing sheets, the typical approach would be to duplicate the original, copy the object over, and then delete the copy of the original (or keep it for future use, either way).
When a user creates a duplicate of a sheet, they are not editing the original and thus have no way of doing harm. The original will remain available for them (or anyone else) to use as a starting point. We use the same approach with Vizlib objects and have never had issues with it, other than users getting overly creative and writing their own (incorrect) expressions, which unfortunately can't be helped.
Hi @Or. Thanks for the quick response. Can you tell me how to set it up in the security rule QMC?
You don't need a specific rule for this. Any user with a Professional license should be able to duplicate sheets by default.
For us, users usually just create a sheet based on the template and work with that. However, if you want them to be able to use the template to add objects to existing sheets, the typical approach would be to duplicate the original, copy the object over, and then delete the copy of the original (or keep it for future use, either way).