Possible Bug: Query Output Unusable, Cannot be Debugged #1170
-
DescriptionI have been using Tabular Editor for debugging issues with visuals. The way I usually do it is to copy the query from Performance Analyzer, running it, and then debugging the results in Tabular Editor. However, this time, with a particular donut visual, I get a non-sensical output: a table with one row, all of the headers say something like [DS0IntersectionCount] or [DS0PrimaryCount], and nothing can be debugged. I cannot rule out that this is simply related to this visual, but I have no idea how to change the query to get any results to show up. Tabular Editor 3 Version3.11.0.26496 ScreenshotsSteps to Reproduce
Expected behaviorAn output table that can be debugged. Crash ReportNo response Windows Version10 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Power BI Desktop is notorious for generating some very ugly queries at times... Note that this particular query returns multiple results (there are multiple EVALUATE statements). In this case, I think the 3rd result set contains the actual data that is shown in the donut chart, and from looking at the query, this result set should also work with the debugger. You can switch between result sets using the numbered tabs on the left of the results grid: |
Beta Was this translation helpful? Give feedback.
Power BI Desktop is notorious for generating some very ugly queries at times...
Note that this particular query returns multiple results (there are multiple EVALUATE statements). In this case, I think the 3rd result set contains the actual data that is shown in the donut chart, and from looking at the query, this result set should also work with the debugger.
You can switch between result sets using the numbered tabs on the left of the results grid: