Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Having a 'master' template, with slaves

Hi all,

I have an interesting problem and I'm hoping for your advice on how to best structure this. I'm looking into source control as a potential solution.

I have to build 30 documents, which will all have exactly the same graphs, sheets, etc... however they will all be loaded with different data (but data will follow same structure) the documents must all have the same design, but feature different brands etc...

My idea was to have a 'master', then ($Include..\) a config file containing all the slave's colours, images, branding etc..

Would source control help with this? I really want to avoid managing 30 documents, which all technically are the same document. I want 1 change to scale across to all the other documents, preferably automagically.

I hope i described this OK and I'm looking forward to discussion on this topic. Has anyone faced any similar challenges?

Thanks,

James.

10 Replies
Joaquin_Lazaro
Partner - Specialist II
Partner - Specialist II

Hi wallerjc:

Read this document: Introduction to Section Access

You can have only your master app, and each of your users will only see his pie of the data.

Hope it helps you.

Joaquín