March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi PowerBI community,
I'm relatively new to PowerBI and have been working through some exercises to get familiar with the tool. I started with the standard financial example (financial.xlsx) and, as a second exercise, attempted to create a report using the Top 250 Series overview from IMDB.
In the process, I utilized the Query Editor to adjust the format of some data. In my PowerBI report, I created a table with relevant information and added five slicers:
For the first three slicers, I created additional tables with the respective values and established relations between these new tables and the main table.
While the Year slicer works perfectly, the Minimum Score and Minimum Number of User Ratings slicers are producing incorrect or no results.
I attempted to troubleshoot by removing unnecessary slicers, leaving only the main table and one of the problematic slicers, but the issue persists.
Another observation is that, even though the table with minimum numbers of user ratings only contains round numbers (e.g., 100, 200, ..., 1000, 1100, ..., 1000000), the slicer displays numbers in between. I'm unsure if this is related to my primary issue.
Any insights or guidance on resolving these slicer-related problems would be greatly appreciated.
Thanks in advance for your assistance.
The way you have created AantalStemmen is incorrect it takes only rounded numbers and when you join(relationship) it with main table the join is only true for rounded numbers and others will get ignored, when you use that column as filter. join only takes exact match. @GMen
10000 is huge gap missing too many values.
try this instead.
Thanks for your response. Although it doesn't explain why the score slicer isn't working.
The idea behind using round numbers was to create a more usable slicer. With small numbers, the gap between them is small, and the bigger the number, the bigger the gap. The filter in the slicer is set to "Bigger than," so I hoped to capture all those results. As I mentioned in my initial post, the slicer is displaying all the numbers instead of only the round ones. If this is impossible, the use of an extra table is redundant. In that case, I can use the field from the original table (and that's working fine).
No SELECTCOLUMNS(GENERATESERIES(10000, 90000, 10000), "Aantal", [Value]), this is 10000 range between 10000 to 90000, and this GENERATESERIES(100000, 1000000, 100000), "Aantal", [Value]) is 100000, this will remove all the values which are 257000, 271000 when you use slicer on AantalStemmen, without AantalStemmen slicer your Score will work fine, but with it it will not due to unavailability of values in it, if no value no relation.
OK, thanks for the help.
But even when I remove the "AantalStemmen"-table (and slicer), the Score-slicer gives a wrong result.
Sorry @GMen Jumped the gun too early, looks like some issue with generateseries , When I use distinct its working fine as expected. Some reason generate series is not refreshing in relationship.
looks like there is known issue with generate series be cautious while using it for floating point values.
I thought you had found the solution for the score slicer because I remembered some of the numbers were ...000000000000001 (and I changed the number of decimals to one). However, I have modified the DAX to:
modify dax to this
ScoreLijsg = DISTINCT(Series[Score])
One thing to keep in mind - anything above 1000 distinct values will cause forced sampling.
change the first and third joins to single directional, from the slicer table to the fact table.
Thanks for your response.
Initially, they were unidirectional, and I modified them to check if it would yield a better result.
However, that wasn't the issue.
Can you share a sample file to review
It is not in pbix format
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
93 | |
92 | |
91 | |
79 | |
49 |
User | Count |
---|---|
160 | |
144 | |
103 | |
72 | |
55 |