Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
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.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 40 | |
| 35 | |
| 34 | |
| 31 | |
| 28 |
| User | Count |
|---|---|
| 137 | |
| 102 | |
| 71 | |
| 67 | |
| 65 |