This feature is must needed so it will be easy to manage access to sheet based on users access using Section Access for Sheet that we can achieved as of now in QlikView.
Sometimes we need to create a special sheet to store objects specially crafted for the report. The sheet doesn't need to be visible for end users, it need to be visible only available for the nprinting account.
I've already used this technique in Qlikview very easy. In Qlik Sense I already implemented using custom properties and security rules, but it´s very complicated to implement in large environments, so I don´t recommend it.
We could have just a visibilty property per sheet like : always , NPrinting, Mobile device ,conditional expression.
I would like this feature but I am very concerned on how to achieve it.
When users are given self-service access to an App, they can duplicate sheets and personalise them - very useful; modern BI approach.
If a sheet is conditionally displayed, should we allow it to be duplicated? (have the same question for those sheets which have on activation actions and/or sheets with buttons) All of this adds a level of responsibility to a user should they decide to duplicate a sheet... is that what we want?
Thank you all for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea.
@pablolabbe - same for us - this is a huge annoyance. Because of the limitations/very strict requirements of NPrinting objects, we very frequently have to make duplicate objects - one for the end user to use in an app and one for a print version. Would be great if we didn't have to do that, but as we do, we need to ensure the NP objects do not get in the way for the end user. We haven't yet gone the security rule approach because it's just extra work and have managed to get away with shrinking these objects down to one cell and tucking them out of the way, but it's not great UX. Having a dedicated sheet that is available to NP but not end users would be excellent.
I too agree with the concept, indeed a great idea. We have a similar kind of requirement where we have 6 sheets in an app and it is in production. Now some of the users from a different BU are questioning like if people from a specific BU are logging in can we hide some of the sheets ?
I think this might be possible using some security rules from QMC but if this is given as in built feature like QlikView then we can handle this with section access.