Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
Hi everyone,
I’ve encountered an issue where the same SQL query yields different results in BigQuery and Power BI. The query includes various aggregations across various tables, and I initially used the GROUP BY ALL feature in BigQuery to simplify my query. However, I noticed that when I run the same query in Power BI (via DirectQuery or importing the data), the results differ from what BigQuery returns. Specifically, Power BI didn't group the data correctly and aggregated the data from two different quarters into the same quarter.
After some troubleshooting, I found that explicitly listing the columns in the GROUP BY clause (e.g., GROUP BY 1, 2, 3, etc.) resolves the discrepancy. This leads me to believe that Power BI might not fully support or correctly interpret the GROUP BY ALL syntax.
Has anyone else experienced this issue or have insights into why this might be happening? I have fixed the issue on my end, but I still wish to fully understand the root cause of the discrepancy.
Thanks for the help!
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 4 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 13 | |
| 11 | |
| 11 | |
| 8 | |
| 6 |