Forum Discussion
Solved
Daisy-Chaining Dataflows
Hi all, I am working with an API that is very finnicky and is prone to timing out, especially when large amounts of data are requested. Unfortunately, for this use case I have to move about 10M r...
solution for this - multiple api calls of a reasonable size, partioning the data.
setup a power automate trigger, when a data flow completes - this will trigger the next flow with the next chunk of data.
setup a final PQ step to append the query results, reference the tables from the partioned API calls. importantly, ensure enable dataload is disabled with all of the query results. append the results.
what do you mean PA? do you have dedicated / premium capacity, i dont think you can reference dataflows from each other without it.
have you should tried combine the dataflows in a power be semantic model? not quite clear what you saying, if you create 10 dataflows in sequence but do no referencing does that help?