Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. 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?
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.