Qlik Community

QlikView Security & Governance

Discussion Board for collaboration on QlikView Security and Governance.


Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

Section Access limitation of 1M rows?

Section Sccess has started truncating my data set now that my app has expanded beyond 1 million rows.

The "hierarchy" of my data looks like this

Client Group



               Case Attribute A

               Case Attribute B


where Section Access is implemented on the level of the bolded underlined text above which is a 1:n relationship. A Client has many Cases but a Case belongs explicitly to a Client. Users are assigned access per Client + Case combination.

A few weeks ago the app expanded beyond 1 million Cases and that's when this issue started occurring. Here is the symptom.

> I reload the app (1,002,500 unique Cases)

> Save the qvw (still 1,002,500 unique Cases)

> Close QlikView and reopen the qvw (now exactly 1,000,000 unique Cases)

If I were to reload again without closing QlikView I would be brought back to 1,002,500 Cases.

Anyone encountered a similar issue?


Tags (1)
9 Replies
Not applicable

Re: Section Access limitation of 1M rows?

Yes, I founded before, 1M max, my workaround was to load the table outside the section access, something like:

section application;


LOAD USER, FilterFields

section access;


So NTNAME filters the USER and from there it applies security.

Hope i explained myself.

Not applicable

Re: Section Access limitation of 1M rows?

Interesting indeed Ruben.

I'll investigate your proposed setup and see if that works in my environment. I'll keep you posted.

Are you aware that this is a known limitation of Section Access, meaning if Qlik has acknowledged this limitation?

Not applicable

Re: Section Access limitation of 1M rows?

Maybe is documented somewhere but I searched and didn't found it. (It was more than one year ago)

Not applicable

Re: Section Access limitation of 1M rows?

DO you have the Section Application executed BEFORE your Section Access part for a reason?

Not applicable

Re: Section Access limitation of 1M rows?

No, it was a document which suffers very upgrades with drastically changes in data, security and usage and to apply one of those changes the simpliest way was to put section access at the end.

Not applicable

Re: Section Access limitation of 1M rows?

Ok. To clarify, it seems that although Section Access supports >1M rows there is a limitation that reduction field(s) in in the Section Access table cannot handle more than 1M unique values. This is where a setup like Ruben Marin suggests above comes into play.

I've got a temp fix in place for now to limit the table to less than 1M unique values and will work on the clean solution in a couple weeks and post the results here.


Re: Section Access limitation of 1M rows?


Do not know if you have seen the following info, but this might help.  You can also leave a post on the blog posts and Henric will likely reply.  I know there is a 2 billion unique data point limitation as per the QlikView Reference Manual in the Appendices, but I am not aware of a Section Access limit, so this could be a defect, and if you are a licensed user, I would suggest you open a support case with us, so we can look into this.  There are some other blog posts here as well that may be helpful to you in understanding things at a deeper level and rather than me trying to find them all, I will let you look at them yourself to determine which ones may help in addition to the ones below:

Primary Design Blog link:


Section Access/Data Reduction links:




I hope this might help, sorry I do not have exact info regarding the limitation you appear to have hit.



To help users find verified answers, please don't forget to mark a correct resolution or answer to your problem or question as correct.
Not applicable

Re: Section Access limitation of 1M rows?

Wondering if anyone can confirm whether a defect was ever found related to Section Access limitations in either QlikView or QlikSense?

Not applicable

Re: Section Access limitation of 1M rows?

I don't know if it can be called a defect but there is a limitation of 1M different values in section access, you can test yourself:



'YourUserName' as USER,

RowNo() as REDUCE

AutoGenerate 1e6+1;

SECTION Application;


AutoGenerate 1e6+1;

After reload, without data reduction Max(REDUCE) will return 1000001, after opening with data reduction returns 1000000.