Using the "Reload" button action with Section Access causes current selections to be lost

[PedroC]

Hello,

This is my second try with this issue (I guess I wasn't clear enough in the previous one)

I've got a very simple app with one table and a section access than manages "Tasks" assigned to users. 

A user must have access to any "Tasks" of one or several "categorys".

My script is just like this:

Section Access;

UserRestrictions:

LOAD * INLINE [ 

     ACCESS, USER.EMAIL, CATEGORY

    'ADMIN', 'user1@yourdomain.com', A

    'ADMIN', 'user1@yourdomain.com', B

    'USER', 'user2@yourdomain.com', C    

];

Section Application;

MainTable:

LOAD * INLINE [

TaskId, Task, CATEGORY

    1, Task 1, A

    2, Task 2, A

    3, Task 3, B

    4, Task 4, B

    7, Task 5, C

];

In the app there's just one table and two buttons to:

• Full Reload. It will reload the app using the "reload" action of the button
• Automation Reload. It will run an automation that reloads the app 

If I select a TaskId and click on the "Full Reload" button the app will reload and all selections will be cleared, but if I use the "Automation Reload" then the app will be reloaded and the selections will be kept.

If I remove the Section Access of the app the "Full Reload" button won't clear selections so it's just an issue related with Section Access.

This app needs to be reloaded on demand many times a day and it might occasionaly reach the limit of 48 daily reloads of the standard suscription or even 192 of premium/enterprise, so "Automated" reloads are not a solution.

Does anybody knows a workaround for this issue. 

Thanks in advance!

 

[jasonmiller11tt234]

This appears to be a limitation of how Section Access works during a Full Reload. As far as I know, there isn't a supported workaround to preserve selections in that scenario. If Automation Reload isn't viable due to reload limits, you may need to redesign the reload process (for example, using incremental loads or bookmarks where applicable). I'd also recommend raising a support ticket to confirm whether this is expected behavior or a known issue.

[PedroC]

Thanks Jason

What makes no sense for me is that reloading an app through an automation works perfectly fine.

I’ve tried with bookmarks. Qlik doesn’t have an action (buttons) to create or delete a bookmark, just to apply a bookmark.

Also tried with automation, using the create bookmark block to get current selections and applying it after reloading the app, but then I’ve found another limitation, the bookmarks won’t exist in the app unless a SaveApp block is called in the automation, and that reloads the app from scratch and selections are lost.

I don’t really get what you mean with incremental load. As far as I know, incremental loads are implemented using partial reloads and they also count for the daily reload limit for Qlik so this is not a way out.

I will give a try with support, but sincerely, I expect a “work as designed” answer.

Thanks!