Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Oct 25, 2022 7:42:43 AM
Mar 27, 2018 7:18:31 AM
In section access, for a single user, it is possible to specify "only" 1,000,000 distinct values for the reduction field(s). After 1,000,000, the values are truncated.
Example script:
//Admin,Service users USERS: LOAD * INLINE [ KEY,USERNAME,ACCESS *,DOMAIN\QVSERVICE,ADMIN *,DOMAIN\ADMINISTRATOR,ADMIN *,INTERNAL\SA_SCHEDULER,ADMIN *,INTERNAL\SA_ENGINE,ADMIN]; //User DOMAIN\AE92242 concatenate LOAD '1-' & RecNo() as KEY, 'DOMAIN\AE92242' as USERNAME, 'USER' as ACCESS AUTOGENERATE 1000200; //User DOMAIN\AE92241 CONCATENATE LOAD '2-' & RecNo() as KEY, 'DOMAIN\AE92241' as USERNAME, 'USER' as ACCESS AUTOGENERATE 1000400; Section Access; load ACCESS, USERNAME as USERID, KEY Resident USERS;
Upon opening the app, both users will only see 1,000,000 values and will be missing the remaining 200 and 400 values respectively.
This is a known and intentional limitation. The section access should contain a comparatively small reduction field that will link to a larger field in the section application, in what is typically defined as a one-to-many relation.
Resources for Best Practice and possible solutions:
Primary Design Blog link: Qlik Design Blog
Section Access/Data Reduction links:
Data Reduction – Yes, but How?
Data Reduction Using Multiple Fields
A Primer on Section Access