Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
Could you please explain what is static and dynamic reduction? when to use it?
Regards,
Sivaraj
Requested examples:
Case #1. Dynamic (Section Access) Reduction (DDR). You have a company with 100's of Sales Reps across 4 sales teams. When opening the Sales.qvw app, each employee role should be limited to seeing the following data.
1. Company Executives -- All sales for the entire company.
2. A Sales Manager -- only the sales for her Team.
3. A SalesPerson -- only sales made by that salesperson.
Every user opens the same Sales.qvw. But the data visible to that user is dynamically filtered to match their role. This is a good case for using DDR.
Case #2. Static Data Reduction (Loop and Reduce). You are a global company with 2 subsidiaries, Company A and Company B. Users should be limited by role to seeing the following data.
1. Corporate users - All sales.
2. Employees of Company A -- sales for company A.
3. Employees of Company B -- sales for company B.
When the Sales.qvw document is reloaded by Publisher, a Loop and Reduce task will input Sales.qvw and output three different qvws that contain data by role.
SalesAll.qvw -- All Sales
SalesA.qvw - sales for Company A
SalesB.qvw -- sales for Company B.
Each user will be granted permission to the document that matches their role. That is the only Sales they will see in Access Point.
-Rob
Hi,
Dynamic Data Reduction
Dynamic data reduction is done in QlikView using the concept of Section Access, which is part of the QlikView document. Meaning there is a single QVW file and all users can access the QVW file and data is reduce based on the access level given i.e. Section Access
Static Data Reduction
For larger deployments and/or those in need of centralized control of authorization capabilities, QlikView Server/Publisher are used. Departments or functions often have a “master” application that contains all relevant data covering all analysis needs, and this master document needs to be separated (“reduced”) according to the needs and access privileges of the intended audience. QlikView Publisher reloads the QlikView document with available data, refreshes the Section Access tables, and splits the large QlikView document into smaller documents based on values in a particular field.
This “reduction and distribution” allows for a file containing many data fields to be broken up by the contents of a field and distributed to authorized users or groups according to their access privileges.
Thanks for your reply. Can you give an example?
Plz go thru the following link to better understand Section Access:
Requested examples:
Case #1. Dynamic (Section Access) Reduction (DDR). You have a company with 100's of Sales Reps across 4 sales teams. When opening the Sales.qvw app, each employee role should be limited to seeing the following data.
1. Company Executives -- All sales for the entire company.
2. A Sales Manager -- only the sales for her Team.
3. A SalesPerson -- only sales made by that salesperson.
Every user opens the same Sales.qvw. But the data visible to that user is dynamically filtered to match their role. This is a good case for using DDR.
Case #2. Static Data Reduction (Loop and Reduce). You are a global company with 2 subsidiaries, Company A and Company B. Users should be limited by role to seeing the following data.
1. Corporate users - All sales.
2. Employees of Company A -- sales for company A.
3. Employees of Company B -- sales for company B.
When the Sales.qvw document is reloaded by Publisher, a Loop and Reduce task will input Sales.qvw and output three different qvws that contain data by role.
SalesAll.qvw -- All Sales
SalesA.qvw - sales for Company A
SalesB.qvw -- sales for Company B.
Each user will be granted permission to the document that matches their role. That is the only Sales they will see in Access Point.
-Rob
Thanks Rob...Great example
Rob in the Case 2 how is the access granted toi the users I do not see anything in the QMC.
When you set up loop and reduce there is no way to indicate wich users can see wich reduced app.
Thanks for your clarificaction
Hector, On the Distribute tab of the task, you will map a reduction field to user names/groups.
-Rob