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
- 10.6K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 477 Transform
- 1.8K Magic ETL
- 69 SQL DataFlows
- 478 Datasets
- 218 Visualize
- 260 Beast Mode
- 2.1K Charting
- 12 Variables
- 19 Automate
- 356 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 249 Distribute
- 65 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 191 Product Ideas
- 1.2K Ideas Exchange
- 11 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive