Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello All,
I have a requirement like, in a single application the section access should apply for few sheets and not for all.
Before it was like document chaining where as in section access application is navigated through a button to another application where it has no section implemented. Below link is helped to understand this
Here the user wants to merge the both application in to single application and conditioned applied with the previous.
Please help me on this.
Thanks
I'd challenge that merging both apps is a good idea, first of all, if only because of maintenance. Is the same data but only certain visualizations that should be shown for some and hidden for others?
Would be useful if you can elaborate on that.
Bear in mind that section access is a special table, but a table after all, like any other in your data model. If the data from both apps have different data models, you will have to create a single data model which serves the purpose of both, then implement security.
Also note that section access filters data if the reduction field is included in its table. If there is an island table, or a second data model (which I would never recommend, but I have seen several times) and fields from such island table or separate data model are not included in the section access, these rows will not be filtered, at all.
I'm saying this because I don't understand how the same model will have the same data exposed to all, and only on the front-end the information is restricted by showing or hiding sheets.
For example, what happens if a user downloads the app? Or if he creates a new field?
Hi All,
Any suggestions on this.
Thanks
Atukuri, check out the following Design Blog post, there are some other links in this post related to reductions too, I am not sure you will be able to pull things off here, but the posts may give you some other ideas:
https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Section-Access/ba-p/1465766
The only thing that just popped into my head is having two different data models in the app, one for the Section Access piece and one without and then ensuring the Section Access table is not linked to the other model, but not sure if this is practical or not...
Regards,
Brett