How to set PDP effectively
Try to explain this as clear as I can: this is a simplified version, I have more data columns need to be considered.
I have a dataset A. I created 3 different dashboards using this dataset A.
Dashboard | Name | Data columns |
all webpages | DA | webpage region, web business area |
campaigns | DB | campaign region, campaign business area |
a group of webpages | DC |
User groups | users |
1 | a |
1 | b |
1 | c |
2 | d |
2 | e |
2 | f |
3 | a |
3 | c |
3 | e |
User group1, 2 have access to Dashboard DA, DB and user group 3 have access to DC.
1. User group 3 who are also in group1 or 2 should have full access to all data for dashboard DC.
2. User group 1, 2 should have access to DA based on web region and web business area;
3. User group 1, 2 should have access to DB based on campaign region and campaign business area;
I am not sure how to handle this. People in the same group are seeing different numbers from the same report because of the PDP setup.
Thank you.
Best Answer
-
Create a View with SELECT * for each dataset and apply the appropriate PDP. Make the default permission of the original dataset NO ROWS.
If certain dashboards need subsets of columns, implement that, it'll deliver the faster view performance.
Consider using the PDP UTIL to automate PDP policy creation
https://knowledge.domo.com/Connect/Personalized_Data_Permissions_(PDP)/PDP_Policy_Autocreation
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
Answers
-
I'm 95% confident that PDP permissions are ADDITIVE (so if i'm I'm in group 1 and group 3 i will see the data available to group 1 AND the data available to group 3).
It sounds like you want to use PDP to provide filtered views of your dashboards and that's NOT the same thing as providing filtered sets of Data. assume that if you give me access to data via PDP i will ALWAYS see ALL the data (regardless how you want to filter my cards.
That said for dataset you could add binary columns to your dataset, ForDashboard1, ForDashboard2, ForDashboard3 then use that column to hard code filters into your dashboards and subset the data with respect to whether you want it shown in the dashboard, but not necessarily tied to a PDP policy.
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
@jaeW_at_Onyx thank you for the explanation. That is probably why they see different numbers.
Creating binary variables in the dataflow is tough for me: because this is a huge dataset with 114 M rows, and we had time-out issue before. So I changed the whole process by running 2018, 2019 dataflows separately (just need once) and stack them using assembler, now I only need to run 2020 data daily and stack them with the historical data. this saved me tons of running time. Therefore, it is not easy for me to modify the code. In addition, I will create more dashboards from this dataset, it will be very challenge to keep adding new binary variables. BTW, I still have not got dataview beta, my CSM said it is closed.
Are there other ways I can do to prefilter out for each group? I am getting so many question recently.
Thank you.
0 -
Create a View with SELECT * for each dataset and apply the appropriate PDP. Make the default permission of the original dataset NO ROWS.
If certain dashboards need subsets of columns, implement that, it'll deliver the faster view performance.
Consider using the PDP UTIL to automate PDP policy creation
https://knowledge.domo.com/Connect/Personalized_Data_Permissions_(PDP)/PDP_Policy_Autocreation
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive