This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowThe Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more
Hi All,
Today I tried to split a complex dataflow into two smaller dataflows, called upstream and downstream dataflow.
In the screenshot, the upstream dataflow has 3 output tables (1, 2, 3) to be referred to (all three as linked entities) at immediate downstream dataflow.
However, I noticed that one of the table data didn't flow in.
I am curious to learn how you split the complex dataflow into smaller, kindly advise me.
Thanks for your reply @AnkitKukreja
Let me rephase my question,
when you deal with a complex workflow with lots of step to extract, merge based off some conditions; the condition is the check point for new subset of data. Since dataflow is chained together, it seems that you can only do single output from upstream to be input from downstream within the same workspace, you basically cannot pass multiple subset data playing as conditional checkpoint to downstream dataflow to continue define your workflow and this make the workflow become huge and complex. How to you split such workflow in your practice when there are multiple inputs needed from the upstream dataflow? Not by the best practice links that you sent and I have read multiple times as it's very basic conceptual suggestion.
Best regards,
R.
Hi @rdnguyen
I hope you did checked some best practices to be used and things to avoid.
https://learn.microsoft.com/en-us/power-query/dataflows/best-practices-developing-complex-dataflows
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 13 | |
| 11 | |
| 9 | |
| 6 | |
| 5 |