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
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 293 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 96 SQL DataFlows
- 607 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 705 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive