Does PDP Automation not work for Dynamic PDP using non-system attributes?

I setup a new Managed attribute called "Region". If I assign a user a value for this attribute and manually create a PDP policy for it, it works as expected. I setup an input dataset to run the PDP Automation on, and while it creates a policy, the user cannot see anything. The policy also looks different. Instead of showing the filter column and attribute name, it shows the filter column and the attribute value/string "domo.policy.managed_Region"
Manual policy:
PDP Automation policy which doesn't work:
Answers
-
Is the key for the column also called "Region"? Or did you set the key as "region"? If you don't remember, you can view it here: https://<instance>.domo.com/admin/governance/attribute-management
Was this comment helpful? Click Agree or Like below.
Did this comment solve your problem? Accept it as the solution!0
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 659 Datasets
- 116 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 82 App Studio
- 45 Variables
- 775 Automate
- 190 Apps
- 481 APIs & Domo Developer
- 81 Workflows
- 23 Code Engine
- 40 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 1 AI Projects and Models
- 18 Jupyter Workspaces
- 410 Distribute
- 120 Domo Everywhere
- 280 Scheduled Reports
- 10 Software Integrations
- 144 Manage
- 140 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive