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.
8 Comments
I'm also experiencing the same, an urgent solution would be great.
We're experiencing the same thing. An urgent solution would be greatly appreciated. The ability for users to select the order of their row hierarchy is a gamechanger and what made the Field Parameter feature so powerful.
Hoping this will be resolved soon, this is impacting our large userbase.
Hi all,
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.
Best regards.
Community Support Team_CaitlynAnonymous
I too am experiencing this issue when choosing a company from my slicer. My slicer is a Master Company table.
Feedback Type:
Frown (Error)Timestamp:
2023-05-19T21:33:47.7162791ZLocal Time:
2023-05-19T16:33:47.7162791-05:00Session ID:
18df616a-902c-4451-8932-2f683e936d06Release:
April 2023Product Version:
2.116.966.0 (23.04) (x64)Stack Trace:
Javascript: TypeError
at VisualSyncService.<anonymous> (https://ms-pbi.pbi.microsoft.com/minerva/scripts/exploreui.js:11874:183)
at step (https://ms-pbi.pbi.microsoft.com/pbi/Web/ts/CefInteropSetup.js:32:23)
at Object.next (https://ms-pbi.pbi.microsoft.com/pbi/Web/ts/CefInteropSetup.js:13:53)
at fulfilled (https://ms-pbi.pbi.microsoft.com/pbi/Web/ts/CefInteropSetup.js:4:58)
at processQueue (https://ms-pbi.pbi.microsoft.com/minerva/scripts/angular.js:18035:37)
at https://ms-pbi.pbi.microsoft.com/minerva/scripts/angular.js:18083:27
at Scope.$digest (https://ms-pbi.pbi.microsoft.com/minerva/scripts/angular.js:19202:15)
at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:350003:106
at ZoneDelegate.invoke (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:103715:180)
at Object.onInvoke (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:335127:64)PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.116.966.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/exploreui.js","Component":"VisualSyncService","Error":"TypeError","MethodDef":"<anonymous>","ErrorOffset":"11874:183"}OS Version:
Microsoft Windows NT 10.0.19045.0 (x64 en-US)CLR Version:
4.8 or later [Release Number = 533325]Peak Virtual Memory:
70.8 GBPrivate Memory:
691 MBPeak Working Set:
0.995 GBIE Version:
11.789.19041.0User ID:
7ea865ce-d7eb-4df4-a42e-729e8104db5fWorkbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.Telemetry Enabled:
TrueModel Default Mode:
ImportModel Version:
PowerBI_V3Enabled Preview Features:
PBI_enableWebView2
PQ_WebView2Connector
PBI_sparklines
PBI_scorecardVisual
PBI_NlToDax
PBI_fieldParametersSuperSwitch
PBI_horizontalFusion
PBI_optimizeTabRibbon
PBI_relationshipEditPane
PBI_setLabelOnExportPdfDisabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_azureMapVisual
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_angularRls
PBI_onObject
PBI_dynamicFormatStringDisabled DirectQuery Options:
TreatHanaAsRelationalSourceCloud:
GlobalCloudRecent Actions:
VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, Set Visual Containers Visibility, VisualContainerUpdateDimensions, CanvasKeyDelete, Set Visual Containers Visibility, CanvasKeyDelete, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistPropertiesDPI Scale:
100%Supported Services:
Power BIHi
The service version is:
Service Version 13.0.20726.71
Client Version 2305.3.13975-trainIt is working properly now, thank you!
Confirmed on our end as well. This seems to have been resolved.
