Liliam_C_Leme MrAndyCutler Maybe I wasn't very clear on my issue...
So just imagine you have a Power BI dataset which is used to visualize the result of the CETAS. So you need to go and refresh the Power BI dataset i.e. daily our hourly. Lets imagine we use another process to kick of the refresh of the query we use with CETAS. It should create always the same file (so that Power BI can consume it) and it should be always there (so Power BI can refresh its data at any time with the latest data the CETAS created, so i.e. if a user presses the "refresh" button outside of the regular reprocess schedule).
So any solution which is renaming the table wouldn't work and if the data isn't available at all time (so as in the original solution in the timeframe the old data was deleted and the CETAS is not done, yet) the Power BI would have empty data.
There's a plentitude of similar scenarios, you might somehow get around those cases by syncing or parametrizing processes but it would be way easier if there's a simple "refresh" option for the CETAS