Criteria-based dynamic content should react to forced criterias from roles

Hi Alexander,

If you use the Dynamic content option "Members" instead of "Criteria", I think you should be able to show the correct department - also when it has been set from Forced criteria.

BR / Ole

Hey Ole

Thanks for replying. You're correct that would fix it.

The problem is, that we need our roles to have forced criterias on different levels of a organization hierarchy dimension - i.e. one role needs a forced criteria on level 2 of the hierarchy, another role needs a forced criteria on level 3 etc. Member-based dynamic content cant handle this, as it requires you to pick a specific level in the hierarchy to show.

If I set the member-based dynamic content to show level 3 of the hierarchy, all the roles which have forced criterias set on level 2, will see a looong line of organizational units of alle the different units on level 3.

I hope this description makes sense.

I presume it's quite common practice to set forced criterias on organizational hierarchies, and that you need to set criterias on different levels of the hierarchy.

I have found a way stacking a lot of "hiding" column chart titles with member-based dynamic content for each level in hierarchy (that hide if they are not unique on their level) stacked on top of each other, on top of a criteria based textbox but it is a lot of work just to have the correct organisation title displayed on a dashboard for every type of manager.

Hi Alex,

Potentially you may also enable the "Single" range setting on the Members dynamic content option - to show nothing when multiple members apply.

In your example, users with forced criteria on level 2 will then see nothing on level 3 - and vice versa.

Of course, this will only work if your forced criteria is set by a single member as well.

BR / Ole

Hi Ole

I tried making a workaround with the "single" range setting as you mentioned.

The problem is the "vice versa" part. If I input member-based dynamic contents for both level 2 and 3 in my header, users with forced criteria on level 3 will see both dynamic content for level 2 and 3, as level 2 is just a single member. Users with forced criteria on level 2 will not see level 3 as it's several members. This is using non-hierarchy dimensions.

I can make it work by adding criteria-based dynamic content at the end (users have the option to digger even deeper in org hierarchy using a slicer), but the header ends up containing almost all the levels in the org hierarchy for the majority of our users, which isn't very user friendly.

And for users with forced criteria it ends up looking like this, because member-based dynamic criteria doesn't have an "no selection" option:

It would be much easier to set up and more logical, if criteria-based dynamic content worked with forced criterias. It is a criteria after all :)