Forum Discussion
Dynamic axis based on user
Hi people,
I want to create a visualisation of which axis change based on the logged-in user.
In my organisation, there are managers and team leads with the following hierarchy.
I want to show the same visualisation, with for example the sales vs budget.
In this visualisation should the manager see the department results and the team leads should see the results per team, like the visual below.
Does somebody know how I could create this graph / model?
I believe that you need a table like this:
ID Category Category 2 E-Mail Project - Team 1 Project Team 1 [email protected] Project - Team 2 Project Team 2 [email protected] Project - Team 3 Project Team 3 [email protected] Maintainance - Team 1 Maintainance Team 1 [email protected] Maintainance - Team 2 Maintainance Team 2 [email protected] Maintainance - Team 3 Maintainance Team 3 [email protected] Project - Team 1 Team 1 [email protected] Maintainance - Team 1 Team 1 [email protected] Project - Team 2 Team 2 [email protected] Maintainance - Team 2 Team 2 [email protected] Project - Team 3 Team 3 [email protected] Maintainance - Team 3 Team 3 [email protected]
You then connect it to a mapping table, with only distict ID's:ID Project - Team 1 Project - Team 2 Project - Team 3 Maintainance - Team 1 Maintainance - Team 2 Maintainance - Team 3
And then you connect the mapping table to your sales table.
Crossfilter direction "Both" on the relationships. And finally you apply RLS on the E-mail column of the first table.
This should mean that if you use the "Category" column you will only see departments as a DM, and only Teams as a TL.
What do you think?
Br,
J
6 Replies
Hi,
You should be able to accomplish this by applying RLS to your model.How does the relationships between "Data" - "Person" - "Team/Department" look at the moment?
/ JThis is the current model:
Currently, no relationship is defined between the Teams and the Employee table.
I'm using RLS to define limit the shown data to the users. E.g.:
User 1: Department = "Project" (because the user should also see the results of other teams in de department)User 2: Department = "Project"
User 3: Department = "Project"
To clarify, one visual should be used and not two.
RLS in this scenario will mean the following:
Department Managers will only see the departments they manage.
Team Leads will only see the teams they lead.
Team Members will only see the teams they are part of.
Does this work for you business case?
Br,
J
I've added the employee table to my last post.
