Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
I was ultimately unable to figure out the root cause of the issue and ended up rewriting a bunch of queries to make this work. The fact that PowerBI fails due to a null exception but never tells you what that null exception is feels really broken.
@RezaAssadi hello,
do you have some dependency on some tables, or are you waiting for some query to finish before you get values for another one, that's the only thing I can think of.
I do have different references between different tables. However, that used to work just fine before and I am not entirely sure why it would only break if I refresh all Data Sources at once (and not when I just refresh this one data source). What's more challenging is that there are no error logs telling me which column has a null reference and where that null reference is. I verified the underlying query and confirmed none of the columns are null.
Check out the April 2026 Power BI update to learn about new features.
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.
| User | Count |
|---|---|
| 44 | |
| 38 | |
| 34 | |
| 21 | |
| 17 |
| User | Count |
|---|---|
| 65 | |
| 64 | |
| 31 | |
| 26 | |
| 25 |