rank function showing wrong rank on access point due to section access

[fashid]

Hi,

I have an application which has rank function in charts and has section access based on branch.

The problem is that, with section access the chart gives wrong rank once deployed on the server.

I am attaching the screenshots of the issue that i am facing .

Could anybody give a workaround for this.

Regards,

nadeem

[Anonymous]

where you are calculating the Rank .. I think in UI ,

Move it to script so that it will calculate before any filter and will not change later.

Thanks

BKC

[sunny_talwar]

I agree with balkumarchandel chandel moving the rank calculation to the script seems like the best solution, if not the only solution.

HTH

Best,

Sunny

[marcus_sommer · Accepted solution]

Depending on the structure of your datamodel and the needs to restrict the access to certain data-areas it could be a possibility to have those data twice within the datamodel. Once with full respect to your section access and a second time in a anonymous or scrambled structure which only serve such special calculations.

- Marcus

[fashid]

Hi Marcus,

Thank you for your reply .

I have already tried the suggestion made by you.

The thing is that when i see the application on the access point the user then sees all the branches,

when in fact he has access to only one branch . I have attached a screenshot of the problem after making the changes as suggested by you .

Regards,

Nadeem

[fashid]

hi Sunnny,

But i have a complex calculation which has multiples tables .

how do i go about doing this in the script.

Regards,

Nadeem

[marcus_sommer]

To achieve the ability to show totals within an application which is section access secured or to compare values on dimensions-level which are the key-fields within the section access you need to include those data a second time and to remove mostly of their datamodel links.

Maybe in this kind that your dimension branch includes all values but by those values which are denied for certain user all further associations (products, store, employee ...) are removed and/or it's aggregated to these level. If this is unwanted you need to replace the other branches with something generic like OTHERS1, OTHERS2 ... or more simply only OTHERS. (I think you will need at least on additional dimension)

It won't be easy to build this and I suggest you checked at first which level of data-views are possible/allowed. I have for example a similar section access case where it is people allowed to see her own data and the data one step above in the hierachy on store-level (each area could see his region, each region could see his channel ...) but on the employee-level each one could see his own data. Then there are further users which could see everything, other everything unless the employees and so on. In conclusion: it's quite complicated and I would it not do again. With the next release from these app I will split them into several apps which then have only simple section access restrictions.

Hope this will help you.

- Marcus