Criteria Based Triggers
Greetings,
It would be great if we could schedule ETL to run on multiple yet very specific criteria. The one I have in mind as an example would be if the data set is not triggered by a prior dataset updating to allow for the system to run it at a certain time. I know we can set it to do this now but in that case it would run twice. I am hoping for something similar to
if dataset update != today then run scheduled time.
Tagged:
0
Best Answer
-
Have you looked into the advanced scheduling options? There are several there which may fit your use case:
Specifically:
- DataSets have updated — This condition lets you activate the trigger when one or multiple DataSets have updated. If you choose this option, you must also specify the secondary condition for when the selected DataSets updated. These secondary conditions are described below:
- Since the last successful run — This option activates the trigger if the DataSets you specify in the condition have updated since the last successful run.
- In the last — This option activates the trigger if the DataSets you specify in the condition have updated in the last insert interval. You can make the interval a number of minutes, hours, or days.
- Within — This option activates the trigger if the DataSets you specify in the condition have updated within insert interval of each other. You can make the interval a number of minutes, hours, or days.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 - DataSets have updated — This condition lets you activate the trigger when one or multiple DataSets have updated. If you choose this option, you must also specify the secondary condition for when the selected DataSets updated. These secondary conditions are described below:
Answers
-
Have you looked into the advanced scheduling options? There are several there which may fit your use case:
Specifically:
- DataSets have updated — This condition lets you activate the trigger when one or multiple DataSets have updated. If you choose this option, you must also specify the secondary condition for when the selected DataSets updated. These secondary conditions are described below:
- Since the last successful run — This option activates the trigger if the DataSets you specify in the condition have updated since the last successful run.
- In the last — This option activates the trigger if the DataSets you specify in the condition have updated in the last insert interval. You can make the interval a number of minutes, hours, or days.
- Within — This option activates the trigger if the DataSets you specify in the condition have updated within insert interval of each other. You can make the interval a number of minutes, hours, or days.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 - DataSets have updated — This condition lets you activate the trigger when one or multiple DataSets have updated. If you choose this option, you must also specify the secondary condition for when the selected DataSets updated. These secondary conditions are described below:
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 602 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 697 Beast Mode
- 43 App Studio
- 39 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 386 Distribute
- 111 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 113 Manage
- 110 Governance & Security
- 8 Domo University
- 30 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive