Section access stops at 415 entries (max. 415 entries)

[ZMI_GmbH]

Hello,

we have a problem with our section access in all documents. We load the section access from our Database like the following:

SECTION Access;

LOAD 'USER' AS ACCESS,
    Upper(WebUser) AS USERID,
    Upper(Password) AS PASSWORD,
    Upper(WebUser) AS US_USER_MA;
SQL 
SELECT * FROM Vi_ST_QV_Benutzer 
Where RTrim(DokPfad) =  Right('$(ADS_DokName)', Length(RTrim(DokPfad)));
 

LOAD * INLINE [
    ACCESS, USERID, PASSWORD, US_USER_MA 
    Admin, QVADMIN, xxxxx, QVADMIN
    USER, QVZMI, xxxxx , QVZMI
  ];

Section Application;
star is *;

Now the problem: If we have more than 415 entries in our Database, the section access stops and only the first 415 entries get loaded. Also the two fixed entries with "QVADMIN" and "QVZMI" are not in the section access if there are mor than 415 entries in the database.

This problem only occurs if we refresh the documents over "ReloadEx" with the Delphi QlikView Component. In the QlikView IDE this doesn't occur.

Sample Call over Delphi:

qlikView.ActiveDocument.ReloadEx(0,1);

Do you have any idea what we could do?

Thanks in advance.

[marcus_sommer]

It looked like the normal QV macro which is based on VBS. Am I right that your Delphi just called such a macro?

What do you mean with that it didn't happened within the QV IDE, a normal manual reload, a qmc reload or macro-reload directly executed from within the qvw?

Usually there shouldn't no differences - if there are it's often caused from the used USER which hasn't the appropriate rights / settings, for example in regard to the used db-driver. One trial could be to use a different error mode and/or to trace the error, number of rows, variable-values and so on - to get a hint by looking into document-log.

- Marcus

[Brett_Bleess]

To Marcus' point, the most likely issue is the fact the service account, QVADMIN has a reduction field value, this is NOT best practice, that account should always have 'blank' in any reduction fields to be certain it sees all values etc., otherwise you can run into situations like you are seeing, so if you still have not figured things out, I would clear the reduction field value for QVADMIN.  The catch to this is that user will only be able to open the QVW via Desktop, it will not open via QVServer if you have the Strict Exclusion option checked in the Document Properties\Opening tab settings, and that is by design.  Please be sure you close out your thread too, if Marcus' post did get you what you needed, you can use the Accept as Solution button on his post to give him credit and let other Members know that worked, if you did something different, please consider posting that and then use the button on that post to mark that as the solution to close out the thread.

Here are some other links that may be helpful:

https://help.qlik.com/en-US/qlikview/April2019/Subsystems/Client/Content/QV_QlikView/Security.htm

https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Section-Access/ba-p/1465766

The latter has a couple other related posts at the bottom directly related to dynamic reduction...

Regards,
Brett