When a user saves a Page Filter - is that just for them for everyone that accesses that dashboard?
I want to build one dashboard for one job title that each has a different brand, and I was wondering if each user saved the dashboard with their specific brand filters on would they stay or would everyone have to keep flipping back and forth?
Thank you!
Best Answers
-
Each user would have to save the page filter they want.
You could achieve what you're asking in two ways.
1: Do as you mentioned. You as the admin would define which fields/columns you allow as page filters and then they as a user would each filter to Brand = Brand X and save the page filter. From then on they would by default see only their brand but could see others if they wanted to. This option is easier to handle with smaller user counts, I could see it being an issue for large user bases.
OR
2: If you only want them to see their brand or just want to abstract the saving of filters away from the end user you can use PDP (personalized data permissions) if you have it to only allow the people/groups to see data related to their brand. This means that in the dataset you would have it set that people with Title X can only access data where Brand = Brand X. Then you don't have to have a page filter since by dataset permissions they can only see Brand X anyway.
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**1 -
To echo the first comment, I'd recommend PDPs or Publication Groups, unless you want them to at least have the option of seeing other brands.
Do they need to have this same data filtered to brand everywhere else in Domo? Use PDPs.
Do they need just this page filtered, and on every data set on the page (if there are multiple datasets used)? Use publication groups.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
Answers
-
Each user would have to save the page filter they want.
You could achieve what you're asking in two ways.
1: Do as you mentioned. You as the admin would define which fields/columns you allow as page filters and then they as a user would each filter to Brand = Brand X and save the page filter. From then on they would by default see only their brand but could see others if they wanted to. This option is easier to handle with smaller user counts, I could see it being an issue for large user bases.
OR
2: If you only want them to see their brand or just want to abstract the saving of filters away from the end user you can use PDP (personalized data permissions) if you have it to only allow the people/groups to see data related to their brand. This means that in the dataset you would have it set that people with Title X can only access data where Brand = Brand X. Then you don't have to have a page filter since by dataset permissions they can only see Brand X anyway.
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**1 -
To echo the first comment, I'd recommend PDPs or Publication Groups, unless you want them to at least have the option of seeing other brands.
Do they need to have this same data filtered to brand everywhere else in Domo? Use PDPs.
Do they need just this page filtered, and on every data set on the page (if there are multiple datasets used)? Use publication groups.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
Aaron,
Thank you for brining up Publication Groups - this is a fantastic idea and greatly supports what I'm trying to do.
Thanks again,
Sam
1
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 50 App Studio
- 39 Variables
- 668 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 45 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 116 Manage
- 113 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive