Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When I loop and reduce by a field does it also loop and reduce the section access data?
QLikView publisher uses the loop and reduce to create multiple documents based on your reduce field. And then when end user access a particular document, based on section access he will see what he is allowed to see.
For example in a typical employee based QlikView dashbaord, I can use the 'Department' field for loop and reduce. Which means that you get a QVW for each department and which would be distributed to the employees of that department. And when an employee of that department access the dashboard, you can use section access to show only data pertaining to him (unless he is an admin).
I hope this helps.
Thanks for the reply, but I think I may need to state my issue in more detail.
I am having an issue where the loop and reduce allows all those in the origonal documents section access to see all looped and reduced documents.
When I open a document that a user is not authorized for they are denied access, but they can still see that the document exists in the access point.
If I explicitly do the section access and document seperation without loop and reduce the access point hides the files correctly.
Wanted to bump this up and add some questions. Is there any documentation that states exactly how loop and reduce works for hidden data like section access? Does loop and reduce only reduce the application data?
Hi Tyler,
As I know, section access is a method of providing user based data access from within the document, where we have the data but we cannot see it if we are not allowed to. As we have both the authorized as well as unauthorized data, 1. the document is not optimized, 2. it possess some amount of security threat.
On the other hand, Loop and Data Reduction works while document distribution. It get rid of data not authorized for a particular user which is an optimized concept as well as much secured.
The idea of brushing the basics is to convince myself of my own understanding which says, they both are different moethod of securing your data. My question is, why would you mix up two different methods to achieve the same purpose? Could you please elaborate the situation that forces you to use both of them?
Thanks,
Anirban
If your problem is that all users see the document existing on accesspoint, have you ensured that DMS authentication is on on the server and 'all authenticated users group' is not allowed to view the document on access point?
Hope this helps.
If your problem is that all users see the document existing on accesspoint, have you ensured that DMS authentication is on on the server and 'all authenticated users group' is not allowed to view the document on access point?
Hope this helps.
If your problem is that all users see the document existing on accesspoint, have you ensured that DMS authentication is on on the server and 'all authenticated users group' is not allowed to view the document on access point?
Hope this helps.
If your problem is that all users see the document existing on accesspoint, have you ensured that DMS authentication is on on the server and 'all authenticated users group' is not allowed to view the document on access point?
Hope this helps.