Refer multiple tables from single upstream dataflow caused downstream blockage
Good day everyone!
I found multiple issues that downstream dataflow didn't get updated data from the upstream dataflow, either in full or outdated.
To describe the case,
Dataflow A upstream performed transformation and provide 2 output tables
Dataflow B downstream from another workspace, referred to both output tables of Dataflow A. Result showed that Dataflow B got stale data from A, which means outdated or sometimes showed as empty table.
Please advise if you encountered the issue before.
2 Comments
- AnonymousNot applicable
Hi rdnguyen
What is the upstream data source for dataflow A ? In what way did you create dataflow B ? If you refresh dataflow B manually, will the data be updated ?
Best Regards,
Community Support Team _ Ailsa Tao - rdnguyen
Helper V
Hi Anonymous ,
Dataflow A referred to another Dataflow X collecting data from SQL On prime, so this mean Dataflow A do its job totally on Power BI Service. Both X and A refresh normal and successfully.
Dataflow B downstream from another workspace, referred to both output tables of Dataflow A. Since in another workspace, B has it own refresh schedule (30 min latency after A)
I tried refresh B manually, one linked entity has data (not all the time), the other linked entity didn't load any at all.