Dropdown slicer malfunction when used for OLAP cube hierarchy fields
Hi,
We are having an issue and I am not sure what might be the reason. When we use a slicer in a dropdown mode for the hierarchy fields (or the entire hierarchy) from OLAP cube (haven't tested this with Tabulars) we see a malfuntion as it changes the displayed text from hierarchy leaf value to hierarchy leaf code, when some other slicer selection chnages.
Slicer settings:
Here is how it looks:
1. Select a hierarchy level in the affected slicer
2. Change selection in other slicer
3. Here is what now displayed instead of value at slicer using hiearchy
This doesn't happen when slicer is in Vertical List mode.
Stan
7 Comments
- AnonymousNot applicable
Hi bodxisatva
What is the version of Desktop that you use for testing? Can you provide your pbix file(remove sensitive info) for testing ?
How to provide sample data in the Power BI Forum - Microsoft Fabric Community
Best Regards,
Community Support Team _ Ailsa Tao - bodxisatvaRegular Visitor
Hi Anonymous
I checked this in two versions of PowerBI Desktop and it behaves the same:
- 2.118.828.0 64-bit (June 2023)- 2.118.621.0 64-bit (June 2023)
This issue also happens with report when it's published to PowerBI web.
Since the report is pulling data from a OLAP cube it's not possible for me to share the pbix file at the moment.
Stan
- bodxisatvaRegular Visitor
Hi Anonymous,
I tried to reproduce this issue against testing OLAP cube based on AdventureDW and it works fine with it.
I will try to look further in our OLAP cubes' setup to see why it could be happening.
Stan
- AnonymousNot applicable
Hi bodxisatva
Hoping this is only an occasional problem. Looking forward to your reply!
Best Regards,
Community Support Team _ Ailsa Tao - bodxisatvaRegular Visitor
Hi Anonymous
I found the reason for such behaviour. If the dimension attribute used in hierarchy has value maintained with different source than a name for it, then it will be behaving in dropdown slicer like I described above.
- Here is the value that set to be using Code filed as a source
If the value for dimension attribute is not mainatained then it behaves normally:
Is this an expected behaviour of PowerBI?
We widely use an approach when Value differs from Name for attributes in dimensions and build a Hierarchies over those attributes. This already gives our buiseness certain discomfort and can do even more in future.
Stan
Stan
- AnonymousNot applicable
Hi bodxisatva
Based on the above information, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
The link of Power BI Support: https://powerbi.microsoft.com/en-us/support/
For how to create a support ticket, please refer to https://community.powerbi.com/t5/Community-Blog/How-to-create-a-support-ticket-in-Power-BI/ba-p/683031
Best Regards,
Community Support Team _ Ailsa Tao - bodxisatvaRegular Visitor
Anonymous
Thank you, I opened a support ticket
Stan