Ragged Hierarchies - Levels generated dynamically

#1

I have question in regards to dynamically generating a Ragged Hierarchy based on Privileged/Non-Privileged access.

At the moment, I have my Ragged Hierarchy setup properly where it’s mapping all of the Parent <> Child Object relationships along with the proper Level Source defined. My setup has 7 Node Levels defined.

Basically I’m going to incorporate this into a Department Dropdown Filter in order to display all of the Parent & Nested Sub-Level departments, so I’m trying to delimit the visibility to departments the user is not assigned i.e. only list out authorized Departments within the Dropdown Filter.

Unfortunately when I apply this clause to the script which the Ragged Hierarchy is derived from, I’m returning empty data being the test user in question is only authorized to view departments starting at Level 4 -> Level 7. In comparison a privileged user will be able to navigate through all department levels 1 -> 7.

I’ve tried different methods as far as embedding this hierarchy into one of the values within the process results of one my cube scripts as well, but unfortunately I came back with an error message in regards to invalid Leaf members I can re-test this scenario and provide a screenshot of the error message if needed as well, however I came back short when adding the hierarchy to the Node Level (Leaf Member).

I can certainly elaborate more on this, but I just wanted to get this question out there and see if anyone has come across this scenario before, and whether they were able to narrow down a solution on how to address it?

#2

Applying security to a ragged hierarchy levels is not supported out of the box. You would need to solve the problem using scripting.

However, ragged hierarchies are loaded completely when they are first used, and having different definitions for each user would be quite expensive.

I would suggest to see if you can split your users into a limited set of categories (based on their privs), then create separate hierarchies/dashboards for each group. You would certainly get better performance if this is doable.

#3

Hey Adrian,

Thanks for your response. I was afraid this was going to be the case unfortunately, so we’ll continue to explore other options such as creating specific Ragged Hierarchies on a group by group basis.