Dynamic PDP
What could be stopping data from showing after applying a dynamic PDP?
I created a dashboard that has about 5 ETL Datasets. I then created a user lincesed group of 27 people and all theses users I created an attribute called GROUPING and assign the locations they can only access or see that locations' data.
I then set a dynamic PDP on each of the 5 datasets using the GROUPING attribute which is based on a location ID. When I preview them in the PDP setting page, it seems to work perfectly.
But when I go to the dashboard where these datasets are feeding to, users aren't able to see data at all, not even data pertaining to their assigned locations.
Strangely, when I toggle users from PARTICIPANT category and assign them as ADMINS they are able to see data.
What could be going on here please?
Any ideas and direction would be greatly appreciated.
Best Answer
Answers
-
The last part is kind of expected, as Admin users will always have access to all data, this is implied in the option step 6 of the guide.
What does your PDP rules look like (sharing a screenshot might help)? I guess you created these in the original dataset and it's then cascading to the ETLs you've created, so it should be in a central place. If you can create a test participant user and switch him to the different "GROUPS" and log in from incognito to see how it behaves that could help a lot.
0 -
@marcel_luthi Thanks for looking into this for me. Below is a screenshot of the PDP rule.
Also, your guess on where the rule was applied, I don't think I applied it to the ORIGINAL datasets. I applied them to the final datasets ETL as that is what is been fed unto the created dashboard. Does that make a difference?And everyone in the USE group has a unique Custom LOCID assigned as below in the personal account profile.
0 -
@carthur all seems good with the setting of the rule, unless there are typos or additional characters that make the values in the LOCID column be different than the ones actually stored on each user in the GROUP attribute 🤔 but lets hope @Ashleigh suggestion solves it for you so you don't have to go too deep into this (QQ if you remove the rule completely, the users able to see the data without you turning them into Admins? I'm sure they do are bothoth worth asking)
0 -
@marcel_luthi Yes when I remove the PDP they see the data and therefore it is clearly something with the BETA function. Contacted DOMO and it has been raised now to the Level 3 at developers' level just FYI.
@AshleighResharing the datasets, to people in the group and also individually still didn't solve it either. Wondering has anyone used this new function successfully?
1 -
@carthur - I'm experiencing something similar with custom managed attributes being used in Dynamic PDP policies (the preview works as expected, but in practice, the user cannot see any rows of data; datasets are shared with the user). Curious, did Domo support resolve this for you already?
For additional context, if I use a "System" managed attribute, it works fine. It is only when I use a custom managed attribute that the PDP does not work.
0 -
@carthur and @adam_mx. Can you please confirm once whether the managed attribute which you have created is not marked with limited visibility?
Attributes with limited visibility are only accessible to the admins and hence I think everything is working fine for the Admins but not for other users.
Reference :
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 296 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 614 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 53 App Studio
- 40 Variables
- 677 Automate
- 173 Apps
- 451 APIs & Domo Developer
- 45 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 32 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive