Hi, I have a requirement to make a certain account name visible only to certain users on our main dashboard, and I'd like to use probably a section access map in script or osuser match() approach on that field and/or related list boxes. It's a very unique scenario I don't expect to have to maintain for any other accounts, so should be manageable as a one-off situation. Also, the account name list box is presently locked to always one value selected to keep people from mixing things up, which should also keep people from indirectly reaching the unseen account's data. (My other option is a clone of the main qlikview that only loads data for this client, but that would be way more effort and future upkeep not specifically requested or required for this scenario.)
I'm going to dig around white papers and old posts now, just posting here too in case someone has a quick answer before I muddle through many other resources.
Hi Massimo, this is close. I also have that section access document. Due to the large number of users involved, I'd like something like a combination of the Omit on Example 5 and the reduction on Example 6 to specify which locations users can see/access when making selections in the location field.
Re-reading Example 6, it looks like I can infer that leaving a blank in that reduction field name means the user can access all values, and listing values constrains users to those values. I may be okay going like:
LOAD * INLINE [
Access, NTName, Location
User, User1, Mercury
User, User1, Venus
User, User1, Earth
User, User2, *
User, User3, *
User, User4, *
And Admin could see all locations including Mars and the outer planets, while users 1-4 can only see Mercury Venus and Earth. (The document says repeatedly that * is only all listed values, and not all values in that field. I'm guessing the empty spot next to admin is a lack of constraints on what people see and am going to test that.)
Thanks Massimo. I'm going with Example 6 at the end of the pdf attachment in the post you sent the link to. Example 5, the Omit feature, looks like it'd be handy to make the same qlikview focus to different functional areas (sales warehouse corporate) while example 6 looks like the way to go for different geographic areas.
(Handed you the correct answer credit because that section access pdf is an absolute must have, and gave myself the helpful for clarifying my own specific situation on the second pass and using a part of the correct answer you provided. )