Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
When I edit a query in Power BI and click "OK" when I am finished the OK Button greys out and I get the spinning wheel that takes forever to move on.
Sometimes it also takes forever to 'evaluate' the queries.
The query itself runs just fine in SSMS and doesn't take long to finish there. However, i've had this take as long as 50 minutes to complete for a query that runs for only a few minutes in SSMS.
Any thoughts or is this a support issue?
Solved! Go to Solution.
@Anonymous
I'm going to assume you are in power query (PQ) here; if I'm wrong I'm sorry.
I ran into this a few times in the past. I used to merge tables in PQ b/c it was kind of convenient & kept me from having to write out the same functionality in DAX. This became an issue b/c I would go in and update my query based on either new requirement or just cleaning things up a bit (or possibly learning of a new way to do things). OMW! After a while I would find myself in your situation; waiting 4 EVS for one thing to change--I mean, this would eat up a lot of my work day.
If this is what you are running into, I recommend STOPPING this in PQ and simply write out DAX in the report that will produce similar outcomes (e.g., lookups, unions, etc). This made my life a lot easier. Waiting for freggin hours for one change when there is an alternate way of doing something that will get you where you need to be & save you time SUX. Your time is too important. Do it in DAX.
@Anonymous
I'm going to assume you are in power query (PQ) here; if I'm wrong I'm sorry.
I ran into this a few times in the past. I used to merge tables in PQ b/c it was kind of convenient & kept me from having to write out the same functionality in DAX. This became an issue b/c I would go in and update my query based on either new requirement or just cleaning things up a bit (or possibly learning of a new way to do things). OMW! After a while I would find myself in your situation; waiting 4 EVS for one thing to change--I mean, this would eat up a lot of my work day.
If this is what you are running into, I recommend STOPPING this in PQ and simply write out DAX in the report that will produce similar outcomes (e.g., lookups, unions, etc). This made my life a lot easier. Waiting for freggin hours for one change when there is an alternate way of doing something that will get you where you need to be & save you time SUX. Your time is too important. Do it in DAX.
I ended up finding a 'work around' that kind of works... Someone posted that if you hit "cancel" when the query is spinning, then close out, and save PBI. Then go back in and refresh the previews of your queries and hit 'close and apply' it seemed to run a little faster.
Thanks for the idea though. I try to do as much as I can without DAX but there is only so much!
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.
| User | Count |
|---|---|
| 50 | |
| 44 | |
| 42 | |
| 19 | |
| 19 |
| User | Count |
|---|---|
| 70 | |
| 68 | |
| 33 | |
| 32 | |
| 32 |