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
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.
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 |
|---|---|
| 36 | |
| 33 | |
| 31 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 66 | |
| 55 | |
| 31 | |
| 26 | |
| 23 |