I am writing to report a bug I've encountered in Power BI service which seems to be impacting the way options are ordered when selected from a slicer.
To elaborate, it appears that the order in which options are selected from a slicer is not being followed as expected. Instead, they now adhere to the order outlined within the field parameters. This deviates from the previous functionality where the options would display in the exact order as they were selected from the slicer.
This unexpected change in behavior is significantly affecting the functionality and user experience of my reports. The ability to have options reflect in the order they are selected is crucial for accurate data representation and interpretation.
Here is a more detailed description of the issue:
- The Bug: The order of options from a slicer are following the predefined order in the field parameters, not the order in which they are selected.
- The Impact: This bug is causing confusion and misinterpretation of data, as it disrupts the logical order in which data is expected to be presented.
- Expected Behavior: The selected options should reflect in the order they were selected from the slicer, not the predefined order in the field parameters.
I believe that this is a bug and not a feature update, as the original functionality provided more flexibility and user control over the display of data. I would greatly appreciate it if you could kindly look into this matter, and hopefully revert the ordering back to the selection sequence from the slicer, or provide an option to choose between selection and predefined order.
I am looking forward to hearing from you and seeing this issue resolved soon.
I wasn't able to reproduce the issue, but I believe it would be due to a different version of Power BI Service.
Can you provide detailed version information (you can find it in the top right corner of Power BI Service > "?" >About Power BI )
Also, it would be more helpful if you could provide some example gifs describing the issue. (Be careful not to include sensitive information)
We will get back to the product team as soon as this issue is confirmed.
Community Support Team_Caitlyn