PDP Util - the effects of the different delete_options in the config dataset
Config and Data Datasets before running the PDP Util
For this I am using a Domo Webform dataset, which works like a Google Worksheet - i.e. you can edit the data without needing to re-upload a new dataset, which resets the dataset ID.
See attached Word file for a better copy of the screenshots.
After run 1:
- Duplicated PDP rule as setting is to “none”, which means don’t touch the existing rules but create a new one. Update will match on the rule name and update the rule to whatever is set in the config dataset
Resetting to update
After run 2
- The 2 rules with same name are deleted and replaced with a new rule with the same name and same config as per the config dataset
Adding a few more rules
- The user ID for your own account can be grabbed from the browser URL when you are at the My Profile page
After run 3:
- 1 rule replaced as per the previous example, 2 rules created: 1 for a single user through the User ID and 1 for a group by the group’s name
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
- 657 Datasets
- 115 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 81 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