Forum Discussion
Scatter Chart Ignoring Visual Level Filter Measure
Hi Anonymous,
I have made a test with a simple data sample on the latest version of Power BI Desktop (2.65.5313.1381), it seems that everything works as expected.
I get data from SQL Server with Direct Query and then create the measure.
Here is my test result.
Please check if you have installed the latest version of Power BI Desktop.
If you still need help, please share a dummy pbix file which can reproduce the issue, so that we can help further investigate on it? You can upload it to OneDrive and post the link here. Do mask sensitive data before uploading.)
Best Regards,
Cherry
- Anonymous7 years agoNot applicable
I don't think I can share a dummy .pbix file, as you will not have access to any of the underlying data sources (composite model with DirectQuery).
Everthing worked fine when I used a small dataset, but after connecting to an Impala server with 2.7B rows, that's when the visual started throwing the error. I also tried Scatter Chart by Akvelon and Spline Chart from the marketplace, same error. Switch the same visual to a line or bar chart and it loads fine. It is as if Power BI tries to pull in all the data first, then use the measure to filter and throws an error first.
-BIPowerUser
- jtownsend217 years agoResponsive Resident
I believe your statement "It is as if Power BI tries to pull in all the data first" is correct.
The if statement evaluates each line, try a switch function. That fixed a similar issue I had before.
Try something like this:Switch( TRUE(), [Distance] <= MAX('Distance'[Distance Away]),1,0)- Anonymous7 years agoNot applicable
I am receiving the same 1M row errror with the SWITCH function as I am with an IF statement. I am also receiving the error when charting the same Depth and Value combo in a line chart. How do I get Power BI or a DAX statement to filter the data and avoid this error?
In DAX studio, if I am interpreting this correctly, I am seeing that the query actualy ignores the Measure used to filter the data on the inner query. Then tries to apply it on the outer query, but throws a 1M row error before it can filter the results.