I'm trying to reduce the data set that users are able to view based on their respective departments. I've tried to use Section Access to limit this by using a REDUCTION field. However upon testing the data sets are not being reduced as expected. I am wondering if using reduction requires the publisher license? Currently we have both the desktop and server license but not the publisher.
Also, I have loaded the section access with UPPER CASE in both the field name and the data. However, the field and the data inside the dashboard are a combination of Upper and Lower case. Would this be causing my issue?
Example load script:
LOAD * INLINE [
ACCESS, NTNAME, DEPARTMENT
USER, DOMAIN\USER2, DEPT_TWO
USER, DOMAIN\USER3, DEPT_THREE
USER, DOMAIN\USER4, DEPT_FOUR
USER, DOMAIN\USER5, DEPT_FIVE
LOAD * INLINE [
Any help would be greatly appreciated!
For "Data reduction based on section access" you do not need a Publisher license.
Field names and the data in the fields are CASE sensitive. To solve this issue, make a conversion table: Make a table with both DEPARTMENT and Department with the values you use in the Section Access table and the real values.
It appears I needed a combination of both the above responses. In addition, I found that I needed to use an INLINE load of the Section Access as the load from .xlsx didn't seem to work (even with the UPPER() function?). At any rate, thank you very much gentlemen!
If you cannot read directly your XLSX, have you tried to first load it in a table outside the section access, and then use it in the section access with as a Resident? Of course don't forget to drop the first table before exiting the script.
You can do the data reduction in two ways using the QMC and SECTION ACCESS, If your using SECTION ACCESS no need if the QMC or Publisher. For Section access to work, all the data in section access need to be in Upper case if not you need to convert your data accordingly.
To answer your question"Section Access as the load from .xlsx" will definitely work , can you please share the file? or make sure your following all the rules .
Create a link between DEPARTMENT and Department like this:
LOAD Distinct Department,
Upper(Department) As DEPARTMENT
Resident [Actual Dataset];
You could also create DEPARTMENT as a derived field when loading the fact table.