Qrew LegendI understand that you want to have a set of foundational reports and don't want to replicate them N times for each different Product Team.
I have this exact situation in place with one of my clients where for some Roles, staff is typically associated with a branch, and they are typically only interested in records for their own branch.
I suggest that you create a table a users whee the Key Field is either the users email address or the userid.
Then you load that table with the employees preferred Product Team(s).
then you make a relationship to any of the details tables which end up being displayed as reports on the dashboard where the reference field on the relationship is a formula for the the current user
User()
Then you go back to all of your reports and you add a filter that essentially says the records need to belong to that product team or else the current user has no preferred Product Team loaded. That will cover the situation for higher level managers who cross all Product Teams.
So that your challenge is to determine how you maintain this table of users where the key field is the user ID or the users email address and keep it updated as new employees get on boarded and belong to different product teams.
If you don't have a source available to keep that employee list up-to-date, there are strategies to be able to create a button on the dashboard where when a user presses that button they would add them self to that table and be able to adjust their preferred product teams.
Hi Mark -
Thanks for your prompt reply. You certainly 'get' that we do not want to replicate several dozen widgets and reports 'N' times for 'N' different Product Teams. However our Use Case is slightly different than what you portrayed.
We actually have a Product Team "User Maintained Table' that identifies which Product Team members should be notified of certain events, such as a new Intake. However our Value Chain "Work Groups" are much more broadly defined. And we have numerous Portfolio Leaders who will want to visit various Work Group Dashboards regularly. Thus we do not seek to filter the Dashboard reports by User.
Our Intake Process actually stamps each Project Record with impacted Value Chain(s), Impacted Market(s) and Impacted System(s). Thus we have a an easy key reference field (the impacted Value Chain(s)) that we would like to use to pre-populate the Dashboard filter for each of our Value Chain Dashboards. The actual Dashboard filters work VERY nicely, but I am confident our Value Chain Teams will not want the hassle of selecting the filter for each tab on their dashboard.
I actually want the best of both worlds...... for the Value Chain Dashboards to each provide their filtered KPIs and reports without having the Value Chain teams have to set the filter and without my team having to create literally hundreds of redundant reports.
There must be a way to programmatically 'stuff' the Value Chain into the Dashboard filter as a default (and still allow the user to adjust the filter if they so desire). Thoughts?
I greatly appreciate your input.
Warm Regards,
Qrew LegendIt sounds like you would need a product enhancement, something along the lines of Dynamic Form Rules, except for instead for Dashboards.
my only other thought given that there's probably no magic bullet here is maybe you can provide as simple as possible filter on the dashboard, so tue user just hast to do one click to filter for my favorite product teams.
Mark - The filter on the current dashboard is ultra simple, but still a hassle for Work Group Teams who will view the detail on those Dashboards multiple times per day.
Agree that Dynamic Dashboard Rules would be awesome.
I will speak to the users... I may have to jam more reports and widgets vertically on fewer dashboard tabs to reduce filtering clicks. I really want to avoid the overhead of managing hundreds of redundant widgets and reports.
I submitted the case to QB also. Presume they will simply say this is not current functionality, put in a request (none of my ideas have surfaced that I know of).
