topic Re: Cloud Section Access in App Development

Cloud Section Access

FrankC — Mon, 16 Jun 2025 18:50:40 GMT

I am trying to create section access that is combining and inline table with data from a QVD. However, the data from the QVD is not being applied as expected.

If I put my email in the INLINE table and the application loads as expected. However, when my email is coming in from the QVD, I am getting an error on the load.

Access was denied after reload. Check that the user that reloads the script is included in the section access part of the script. Data has not been loaded. Please correct the error and try loading again.

Re: Cloud Section Access

rafaelencinas — Tue, 17 Jun 2025 00:15:45 GMT

Hi @FrankC !

Follow these steps

1 - Load your QVD Section Access

2 - Create an Order By Statement leaving all users with * in the end

Why

- Section Access reads from Top to Bottom and when you read from QVD maybe the order is ramdom.

- It looks like a "Firewall", block all and only unblock if the rule is written in the right place.

- Instead of * , you can leave blank, it works too.

Bye!

Re: Cloud Section Access

Vegar — Tue, 17 Jun 2025 04:47:56 GMT

In section access all values should be in UPPER case. I notice that you are using `lower(Email)` in your script. Try replacing it with `upper(Email)`.

Re: Cloud Section Access

FrankC — Tue, 17 Jun 2025 13:51:49 GMT

Thank You! What I was having issue with was that the lower case in the INLINE table worked. I used the Qlik Section Access video on YouTube (https://www.youtube.com/watch?v=0VoJPiRrqKA) and the example that is being used had the email address in lower case.

I changed the lower to UPPER on the load script from the QVD and everything is working as expected.

Re: Cloud Section Access

marksouzacosta — Tue, 17 Jun 2025 13:59:52 GMT

Hi @FrankC ,

As @Vegar suggested, use Upper Case for everything. I know a few things changed on Section Access regarding this topic but keep everything upper case, just in case.

I would also suggest making your Authorization table outside the Section Access just for test purposes. Load the way you are expecting and check the results. Then you can move the logic inside the Section Access - be aware sometimes the logic that works outside the Section Access will not work inside Section Access.

Regarding * vs blank, those have different meanings in Section Access, depending on the ACCESS value.
For ADMIN, blank means no restriction, every single possible value from the source will be included during the loading/opening of the app. Blank only makes sense when used together with ADMIN users.

* on the other hand, means all values listed on the column and it make sense to use both with USER and ADMIN ACCESS values.

Regards,

Mark Costa