Locked selections affecting Section Access during (partial) reloads

[LRuCelver]

I encountered this weird behavior where locking a selection in an app with a section access causes the field to be "included" in the section access after a (partial) reload. The only available values after the reload are the ones that have been locked. This even happens during a partial reload if nothing is being loaded.

From what I can tell, this weird behavior is caused by the two tables I'm restricting with the section access being not connected through normal fields. The only link they have is the access table.

Most interestingly, the order in which the fields used for the reduction are loaded into the section access table seems to matter. I've included a small example below.

SECTION ACCESS;
//	This Access Table will work as expected
// 	LOAD * INLINE [
// 		ACCESS,	USER.EMAIL,				SEC_ALPHA,	SEC_NUM
// 		USER,	USER@MAIL.COM,	1,			0
// 	];

//	This Access Table will cause the weird behavior
	LOAD * INLINE [
		ACCESS,	USER.EMAIL,				SEC_NUM,	SEC_ALPHA
		USER,	USER@MAIL.COM,	0,			1
	];
SECTION APPLICATION;

DIM_ALPHA:
LOAD * INLINE [
	ALPHA,	SEC_ALPHA
	A,		1
	B,		1
	C,		2
];

DIM_NUM:
LOAD 
	RecNo() - 2 AS SEC_NUM 
,	RecNo() - 2 AS NUM 
AUTOGENERATE 3;

1. Starting point: Making and locking a selection.
   
2. Reload the app (full or partial reload)
3. Observe how the filters/field contents have changed.
   1. After a reload with the first access table, all filters are cleared. All values are still available as expected.
      
   2. After a reload with the second access table, the locked filter remains and only the filtered values are available.
      

Can anyone reproduce or explain this behavior, or is this a bug? Any help is highly appreciated.

[LiviaC]

Good evening,
I encountered the same problem just today, and found this thread looking for a solution.
Can anyone help with this?

Thanks, 
Livia.

[Frank_S]

Qlik Sense or Qlik Cloud?

[LiviaC]

Hi Frank, 
for me it's Qlik Sense and I'm using an older version (May 21).

[Frank_S]

Ok for you @LiviaC I would suggest that the problem could be with your version of Qlik Sense as that version is more than a year out of support.

You can try patching in the May 2021 track (if that is even available) or suggest upgrading to a recent supported version of Qlik Sense and retesting.

It will be interesting to hear if @LRuCelver is also on an out of date version. 
Kind regards.

[Frank_S]

Ok I've tested in Qlik Cloud and got the following which appears to be a similar result.

However, it seems that the interaction of locked fields and section access is resulting in this behavior which appears to be working as designed. It showing only the fields that are locked and that you have section access permission to.

If you feel this is not expected behavior, please start a support case at your convenience.

Kind regards...

[LRuCelver]

Hi @Frank_S,

thanks for your response.

I'm encountered this issue on a Qlik Cloud tenant.

Are you sure this is really workind as intended? I granted myself access the the ALPHA values 'A' and 'B' as a user. After selecting one of them, locking the selection and reloading I'm no longer able to access the not-selected value. Even after unlocking the selection. This even happens during a partial reload when no part of the script is active.

Since I don't encounter this issue if I give myself access as an admin, I'm fairly certain that the section access is somehow being affected.

[Frank_S · Accepted solution]

@LRuCelver and or @LiviaC 

I received some feedback from internal teams over the weekend. Please go ahead and start a support case at your convenience.

Kind regards...

[Flash222]

Hi, same weird situation. If you lock selections in some fields and reload the app, the fields stay locked, but there are no selections applied. Usually you can't lock a field if no value is selected. This situation leads to the fact that selections cannot be applied in the mashup after connecting to the app, since some fields are locked immediately after opening. This has been causing us a lot of trouble lately. Some additional info:
- The app has Section Access on several fields;
- There are several alternative states in which selection and locking are performed;
- Reloading the app after clearing selections and unlocking the fields does not always help, but we found a workaround on how to reset this state;
- Qlik Sense (February 2024 Patch 4);