Load script / visualization changes across multiple apps

[ScottS28]

In our environment we have many streams that have permissions for individual users to track commissions.

So for example, if we have 15 employees and 2 sales managers, we have 15 streams (one for each employee). Each employee only can see their own stream, and each sales manager can see the streams for the employees under them.

We are changing how our commissions process is represented in our data warehouse and so need to update our queries and some visualizations in Qlik Sense.

When this was originally developed several years ago, the approach was to develop a single template that queries a table and have the loadscript designate which employee to use based on their emp_id i.e.

SELECT * FROM commissions WHERE emp_id = 'employee'

Ideally we keep the same process: develop a new template, adjust the query for each employee based on the emp_id and publish to individual streams

What is the best way to deploy things like this in large groups? We have a lot more than 15 employees in reality so doing individual publishing processes will be cumbersome, especially if we plan to regularly release updates to the template.

[mikaelsc · Accepted solution]

there are/were automation "solutions"/demo's available... https://github.com/QHose/QRSMeteor 

https://integration.qlik.com/useCaseSelection 

but have you considered the good old section access? 

[akshatagrawal]

Hey, have you explored section access.

if no, please explore section access and implement it on emp id of the user who logged in.

Thanks & Regards

Akshat Agrawal

[ScottS28]

Thank you both @akshatagrawal and @mikaelsc I will look more into Section Access.

I looked very quickly at the documentation on Section Access and if I'm not mistaken, it works on a single app that everyone has access to, but controls what data to display depending on the user who is accessing it.

In our scenario we may need to maintain different streams, one for each employee.

Section access doesn't seem like it would help in this case, am I correct?

[mikaelsc]

indeed. if you need to keep different streams per employee, it would be "useless"

(but then again, you could publish the same app - with section access definition - to all the streams... and you'll have kind of a "double" access restriction (Stream  and App; counterside is that you'll end up with many BIG (ish) apps with useless data for most users in their streams. 

or you review your streams "policy" as well. (i tend to prefer to group Business "Themes" in streams; adding access/security rules to apps themselves ("everyone" can see the streams, but not all apps in streams are visible for everyone, and not all data is visible for everyone that can see the app,... etc) 

[ScottS28]

Thank you @mikaelsc that is a good suggestion! I appreciate your thoughts.