Update Triggers to use data refresh instead of requiring a change to run an ETL/SQL.

dale_whitchurch

Currently, when selecting datasets to use to trigger the run of a dataset, all of the input datasets must "change" instead of just run. The ideal use case for this trigger is that a single run of an ETL or SQL execution will be created once all datasets have been allowed to refresh, even if data has not changed.

So the ideal behavior would be that when all of the datasets have run, regardless of the outcome, if at least one of the datasets that have been flagged have changed, run the ETL/SQL to ensure the correct data output.