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
- Product Ideas
- 2.1K Ideas Exchange
- Data Connections
- 1.3K Connectors
- 309 Workbench
- 17 Cloud Integrations
- Data & ETL
- 2.3K Magic ETL
- 120 SQL DataFlows
- 666 Datasets
- Visualize & Apps
- 90 App Studio
- 198 Pro-code Components
- 2.6K Charting & Analyzer
- 873 Calculations & Variables (Beast Mode)
- AI & Data science
- 23 Domo AI & AI Chat
- 4 Managing AI
- 18 Jupyter Workspaces
- Automate
- 122 Workflows
- Alerts
- Distribute
- 118 Domo Everywhere
- 284 Reporting
- Manage
- 145 Governance & Security
- 489 APIs
- 11 Add-ins & Plugins
- 13 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 118 Community Announcements
- 5K Archive