Timing Rules for Element Dependencies within a Data Collection Trigger
Our daily-reporting-refresh trigger has 8 elements. There are some dependencies between those elements. For example, one element brings in data from an external DB while other elements query against that data, creating a dependency.
Should we create new triggers to handle the dependent elements and set up trigger dependencies? Or is MI aware of the dependencies and therefore runs the elements accordingly?
Here are the system timing rules for data collection triggers:
1. Elements that are sourced from an external DB or the Dashboard DB are processed first.
2. Elements that are sourced from Existing Metrics or Reports are processed last.
If your dependencies are more complex than that, then you will need to set up one or more data collection triggers and therefore explicitely set trigger dependencies. Please contact firstname.lastname@example.org for any additional questions.