Section access reduction for a dimension broken when some value is not present

[jldengra]

Hello,

I am working with a section access that makes a reduction in the data for different dimensions. It has been working properly during months, but now I found a scenario where the reduction is broken and not applied.

It occurs when, for a particular user, in the section access table that limits on a dimension I include some records for this user and different values of the dimension, and not all the values exist in the data model loaded after into the application section.

Let's say, for example, that the dimension is the geographical area, and I am loading in the section access a table that limit a particular user to the ASIA, EUROPE and AFRICA regions by three records. The fact is that it works fine if all the geographical areas are found in the rest of the model, but it fails if any is missing so if there are no records related to AFRICA in a particular instant and the document is reloaded, the section access doesn't limit this user on geographical area, allowing he/she to access to all the geographical areas, even when there are two other records in the section access trying to limit he/she to ASIA and EUROPE and there are related record to them.

Is there a way to avoid this behaviour and ensure the section access apply all the existing values reductions even in the case that one of them is not present ?

Thank you in advance.

[vikasmahajan]

Dear Sir,

1. Copy QV document ->

2  Unapply all section access settings

3  Reload

4  Save Document

5 Again Apply Section Access >

6 Reload by ticking -> Doc Setting -> initial Data Reduction Based on Section Access &  Strict Exclusion

Hope this help you

Vikas

[jfkinspari]

Have ticked the checkbox Strict Exclusion in the tab Opening in the Document Properties?

I guess, that if none of the listed geo areas that the user are allowed to see, exists in the model, then the user shouldn't be allowed to access anything.

[jldengra]

Thank you for your help, but strict exclusion is not intended to be applied here because all the non-limited users need to be able to see the unreduced data if there are no matches. Anyway I checked this setting and made a test but the problem persists.

I have delved into the problem, and it is not related to non-present values of the dimension as I thought.

Namely, there are 26 possible values that need to be restricted for the dimension, and 22 of them are properly reduced by the section access, but 4 of them are not been limited. One of the four cases is what I mentioned that the dimension value is not present in the rest of the model, but in the other three cases the value appears, so I have no idea what is really happening.

Have you ever run into the problem that your section access does not work just for some values ?

[Anonymous]

Try to replace "data reduction on open" with "data selection".  Obviously it doesn't fix anything, but you'll be able to see what in fact is going on.  Sometimes the problem is not where we think it is...

Regards,

Michael

[jldengra · Accepted solution]

Finally the problem was related to an internal mapping that transformed the original value for the dimension, and it was not properly applied for the section access related field.

The reduction was not applied for some particular dimension values because they are not present in the data source and only appear after applying a mapping that was missing for the section access related field to limit for this dimension.

It was difficult to detect since the field shown in the document for this dimension was properly mapped.

Thank you all for your help,

Best regards,

J.L.Dengra