Currently we have a Domo view that is comprised of 4 or 5 different datasets. These datasets individually refresh the time between the first dataset updates and the last one updates is about 5-10 minutes. I have ETLs that have this singular view as my source input, if I put a trigger condition on it for when datasets update, the ETL runs 4-5 times a day, once for each time a root table being consumed in the view updates.
I am suggesting that from the magic ETL trigger window we be able to trigger the refresh not on when the view updates, but when the root tables update. From the example above, instead of my ETL refreshing when vw_marketing_unified updates, I want my ETL to allow me to choose from the 4 source tables of the view. Even though I don't have those 4 datasets in my ETL, they are a dependency item that I need to have updated prior to my ETL running. I know I could do a timed/scheduled refresh, but I am not wanting to go down that road yet.
A more advanced idea would be to build something like the data driven subscriptions of SSRS allowing users to create a log (or expose domo's native real-time log) of dataset updates, and allowing users to write a SQL case statement saying where tables xyz all have update date = currdate then true. This escapes the need to determine lineage and gives us the flexibility to choose what datasets need to be updated before our ETL can run regardless of if there is a direct relationship
