This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Have you ever combining tables and downstream you realized the joined fact table has multiple null value?
I wonder where else I could find a more complex diagram other than this one from @BIpolar Matthew Roches.
Such as F provides 2 output tables, both of which consumed by G at downstream, G was found with stale data occasionally in one of the output table, the refresh was successfully but data in one of the output is never refreshed.
Another case is E pass on data to F and X pass on data to Y; then E has output referred by Y; and F output is referred by X;
E and F in the same workspace; X and Y in another workspace; Then stale data occurred at Y which made me think the reference was treated as crisscross eventhough they are at different workspaces. Any suggestion?
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 10 | |
| 8 | |
| 8 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 49 | |
| 27 | |
| 24 | |
| 20 | |
| 20 |