Qlik Sense Section Access

[MK9885]

Hi All,

I've successfully applies section access to my test application. I used OMIT and Reduction fields and it is working fine.

But the problem is in from end the fields which I OMITTED to a user is shown as 'Invalid Dimension'

This is not what I want, I do not want that field to appear at all in front end, just like in QlikView.

Am I doing anything wrong here or this is normal Qlik Sense behavior? Cus when we Omit a field it should disappear for the given user but not say 'Invalid Dimension'

Thanks.

[shraddha_g]

This is normal Behavior..

[Miguel_Angel_Baeyens]

It happens the same in QlikView, the field is not there. So if your chart uses that field as dimension, the chart will show unexpected numbers because practically, the field under OMIT is no longer part of the data model. But there is no error message, even if numbers do not make sense.

In Qlik Sense, however, there is this message where the object is defined with a field which is no longer there, telling you need to fix the object in order to display data.

[jonathandienst]

In Qlikview, I would use a conditional for that dimension (or a conditional show of two objects) using a conditional expression like:

     Alt(Count({1} <omitted field name>), 0) > 0

to test whether <omitted field name> is present or not. Perhaps this will help you get started on a QS solution.

[MK9885]

That's not good at all.
Omitted fields should not show at all in Qlik Sense. What is the purpose if you cannot hide the field but instead making it worse by showing an error to users?

They should probably fix it. Users do not want any error message in front end, it confuses them and make developers look as if the job was not done well in front end.

[MK9885]

Will try that and update it...

Thanks.

[Miguel_Angel_Baeyens]

It also confuses seeing the wrong numbers.

You can raise that with Qlik Support because they are the only ones who can fix it.

Just to be on the same side, one thing is hiding a field (using a prefix or a suffix), so the user does not see the numbers but can be used for a calculation, and another is removing a field completely from the data model so its values will not appear in any calculation.

The latter means at the very least that the expression syntax is wrong, because it is using a field which is not in the data model, so I would not be surprised to see an error there.

Yes, I know the differences with QlikView but again you might ask Support if this behavior is on purpose or an actual bug.

[jaimeaguilar]

HI,

like it is already being said, this is the normal behaviour. I don't think Qlik will solve this because it is working "as expected". However, it would be great if Qlik can give you a workaround or an alternative for this issue, so you can share it with us,

regards