Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
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
Hi everyone,
I’m currently working on a Power BI dashboard where users need to select multiple labels and the order of selection or typing matters because it defines the priority of releases.
I have a slicer/filter that allows selecting multiple values such as:
eDR11.1
eDR12.1
eDR16.1
eDR17.1
Users can either:
click the values in the slicer, or
type/paste a list of releases.
Selected FixVersions =
VAR SelectedVals =
VALUES ( TestPlan_ReleaseLabelDim[Label] )
RETURN
CONCATENATEX (
SelectedVals,
TestPlan_ReleaseLabelDim[Label],
" | "
)
Power BI does not preserve the order in which the user selects or types the values.
Example:
User selects:
eDR12.1
eDR11.1
Expected result:
eDR12.1 | eDR11.1Actual result returned by Power BI:
eDR11.1 | eDR12.1Is there any way in Power BI to:
Preserve the order in which items are selected in a slicer, or
Capture the sequence of typed values in a filter/search box, or
Access the selection order via DAX or Power Query?
Solved! Go to Solution.
hi @lnofficial
This isn't currently possible. Power BI does not remember the order in which slicer selections are made. The values if concatenated are sorted in ascending or descending order or by another value.
Hi @lnofficial , Thank you for reaching out to the Microsoft Community Forum.
Even if the rank needs to be defined dynamically, the core limitation still remains, Power BI slicers only return the set of selected values, not the order in which they were selected or typed. That interaction sequence isn’t stored anywhere in the model, so DAX or Power Query cannot retrieve it. Because of that, the priority cannot be calculated from the slicer itself. If the order matters, capture it explicitly, for example by letting the user assign a priority/rank through a parameter or a small disconnected table and then use that priority column to control the ordering in CONCATENATEX.
Hello @lnofficial,
Hope everything’s going great with you. Just checking in has the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.
Thank you.
Hello @lnofficial ,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
Slicers do not preserve or expose selection sequence. If the sequence matters, you need to model it explicitly as a priority/rank rather than relying on slicer selection order.
In my case, I would like to model/set the rank as the user chooses. i.e., there is no static rank for the labels. I will have to calculate them dynamically too.
Hi @lnofficial , Thank you for reaching out to the Microsoft Community Forum.
Even if the rank needs to be defined dynamically, the core limitation still remains, Power BI slicers only return the set of selected values, not the order in which they were selected or typed. That interaction sequence isn’t stored anywhere in the model, so DAX or Power Query cannot retrieve it. Because of that, the priority cannot be calculated from the slicer itself. If the order matters, capture it explicitly, for example by letting the user assign a priority/rank through a parameter or a small disconnected table and then use that priority column to control the ordering in CONCATENATEX.
hi @lnofficial
This isn't currently possible. Power BI does not remember the order in which slicer selections are made. The values if concatenated are sorted in ascending or descending order or by another value.
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.
| User | Count |
|---|---|
| 44 | |
| 43 | |
| 38 | |
| 19 | |
| 15 |
| User | Count |
|---|---|
| 68 | |
| 64 | |
| 31 | |
| 29 | |
| 24 |