Possible to have application launch with the specific user's data, while still having full access?

[ncarson4]

Hi Qlik Gurus,

Wanted to check with y'all to see what would be the best way of responding to a client's request that the application start with a specific user's data visible, while at the same time allowing the user to explore into higher departments and enterprise metrics.

So for Example:

I am Employee A, mailed a link to the QlikView application. I log in to check and when I log in, the app opens with my (Employee A) data pre-selected. 
They still have access to look at their department and others as well as the enterprise.

Employee B is mailed the a link to the same application and when they open it  they first see their data (Employee B) pre-selected. 
They still have access to look at their department and others as well as the enterprise.

I would assume the solution would require some manipulation of Section Access, without restricting anything but utilizing QVUser() in a trigger to match the employee field with the QVUser() field?

Any help letting me know if I am on the right track or an easier solution available would be highly appreciated.

Thanks so much,

Neill

[NadiaB]

Hi @ncarson4 

This post might help if you want to sent a URL

https://community.qlik.com/t5/QlikView-Integration/URL-Composer-compute-an-Access-Point-link-and-pas...

Other option would be to use the OSUser and have any filter that when the application Opens sets the selection to that value. 

QLikView Desktop\Settings\Document Properties\Triggers tab, then select "OnOpen", Add, "Select in field" and provide the field and the value.

OnOpen option is not supported in Ajax.

Kind Regards.

[Vegar]

You could implement an Section Acces without reducing data, but only letting the Section Access set the default selection for the user. See attached picture below.

[Brett_Bleess]

If you have a Publisher license, another way would potentially be to use the Loop and Reduce/Loop and Distribute feature there to do what you want, the trick at that point would be getting the data model hooked into each specific user such that only their data shows there, but they can get the aggregated views as well, that part may prove a bit tricky.  I just wanted to toss this out as another potential option for you.

Regards,
Brett