Forum Discussion
Advocate IVDataflows refresh for linked entities failing
I originally used this architecture too.
As you've noticed, when your first A Level dataflow starts refreshing, it puts a lock on downstream dataflows in the same workspace...so if the second A Level dataflow tries to refresh, it won't be able to get a lock on the B Level dataflow and will fail.
My workaround has been to create another workspace--my "publish" workspace--that has your B Level dataflow with all the A Level entities contained as Linked Entities.
B won't automatically refresh with the A Level dataflows, but since all B contains is Linked Entities, a scheduled refresh should run quickly.
With the B Level dataflow removed from your inital workspace, your A Level dataflows will be able to refresh concurrently.
Also, you could look at using MS Flow/Power Automate or Logic Apps to orchestrate a more granular refresh schedule--you can trigger Power BI refresh from both 🙂
Solution SageI originally used this architecture too.
As you've noticed, when your first A Level dataflow starts refreshing, it puts a lock on downstream dataflows in the same workspace...so if the second A Level dataflow tries to refresh, it won't be able to get a lock on the B Level dataflow and will fail.
My workaround has been to create another workspace--my "publish" workspace--that has your B Level dataflow with all the A Level entities contained as Linked Entities.
B won't automatically refresh with the A Level dataflows, but since all B contains is Linked Entities, a scheduled refresh should run quickly.
With the B Level dataflow removed from your inital workspace, your A Level dataflows will be able to refresh concurrently.
Also, you could look at using MS Flow/Power Automate or Logic Apps to orchestrate a more granular refresh schedule--you can trigger Power BI refresh from both 🙂