Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
I am having issues with capturing the 90th percentile of a given set of data. I have used all the percentile forumals below with no luck. While it returns results, they seem to be incorrect.
Below is a certain set of data where you can see the results of the forumla are returning incorrect results as I did the calculation manually on paper. As you know a normal 90th percentile formula would be calculated as the following steps.
Based on the images below I would assume it would be 110 or 118.
Solved! Go to Solution.
Yes. If you do not already have an Index, you can create a Calculated Column as follows.
NOTE: I am assuming you have an ID in your table. Since you have duplicate values in the Unit Turnout Time, you need a way to differentiate between duplicates to assign different ranks for the same Unit Turnout Time. In this example, I'm simply adding the ID to the Unit Turnout Time to get a unique value on which to properly rank all values.
Once your Index column exists, just update the measure to refer to it inside the CALCULATE.
Hope this makes sense.
Nathan
Yeah, I'm out of ideas unfortunately.
A solid data source should have a unique ID column in each table in the model.
Without a unique ID, we have no way of ranking the Unit Turnout Time due to duplicate values.
And without being able to rank the values, how can Power BI be able to identify the Nth value in the list (in this case the 21st)? It cannot.
Perhaps someone else in the community knows of a different route to take?
I am sorry I was not able to provide a solution.
Regards,
Nathan
Don't be sorry, you helped tremendously. I will work on seeing if I can get a unique ID to drop in with the data.
Yes. If you do not already have an Index, you can create a Calculated Column as follows.
NOTE: I am assuming you have an ID in your table. Since you have duplicate values in the Unit Turnout Time, you need a way to differentiate between duplicates to assign different ranks for the same Unit Turnout Time. In this example, I'm simply adding the ID to the Unit Turnout Time to get a unique value on which to properly rank all values.
Once your Index column exists, just update the measure to refer to it inside the CALCULATE.
Hope this makes sense.
Nathan
@WinterMist - I am not sure if what I am trying accomplish is going to work or either i'm losing faith. I don't have any sort of ID in the table either. Here is a quick snipit of the actual table and the sepcific data in said table.
So for example, each unit has its own turnout time for each specific incident. I am wanting to take the turnout time for said unit and display it in th e 90th percentile accounting for specific slicer filters (that is another conversation).
@WinterMist - I attempted to use the formula you added above, it returned no value under 90th Percentile.
That is because of the highlighted line in your measure below.
The CALCULATE is asking for the Unit Turnout Time where Unit Turnout Time = 21.
But there is no value in Unit Turnout Time of 21. So it returns nothing.
Instead, you want to get the Unit Turnout Time for the 21st record in the list.
This is why I used an Index / Linenumber column, that simply tells you what the linenumber is.
The highlighted line in the measure below is asking for the Unit Turnout Time WHERE Index (i.e. Linenumber) = 21. In this case, Index 21 exists, and is able to find the result.
Does this make sense?
@WinterMist - Yes it makes perfect sense so my question is how can I take the following data and 'select' the right number? Do I need to add an index colum so each turnout time has a specific index number to go with? Ultimately I would like like for it to display the number selected vs showing the entire list of turnout times.
I am open to communicate elsewhere if we need to.
User | Count |
---|---|
51 | |
38 | |
20 | |
14 | |
13 |
User | Count |
---|---|
96 | |
71 | |
29 | |
20 | |
13 |