Semantic data Model

[Anonymous]

Hello,

I have created a new Power BI report using an existing semantic model as the data source. Additionally, I have copied visuals from an existing report into the new one. However, I’m encountering an issue with the slicer. Specifically, when I copied the slicer, it defaults to displaying only one value and does not show all available values, despite the slicer being set to single selection mode.

Has anyone else encountered a similar issue? Any advice or suggestions would be greatly appreciated.

[v-kpoloju-msft]

Hi @Anonymous,
Thank you for reaching out to the Microsoft fabric community forum. Thank you @Visharavana, @Cookistador, for your inputs on this issue.
After reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:

Although you mentioned that the slicer is set to single selection mode, it would be beneficial to double-check the slicer settings. Select the slicer, navigate to the "Format" pane, and ensure that the "Single select" option under "Selection Controls" is enabled. Try toggling it to multi-select and back to see if this resets the behaviour.

Verify that the field used in the slicer is still properly connected to the data model. Any changes or updates in your semantic model might affect the slicer's value display. Check for filters or hidden relationships that might limit the available values in the slicer.

Copying visuals between reports can sometimes cause unexpected behaviour due to caching issues. Clear the cache by going to File > Options and settings > Options, then under Global > Data Load, click on Clear cache to see if this resolves the issue.

If none of these step’s work, consider deleting the slicer and recreating it from scratch. There might be a lingering issue with how the slicer was copied, and starting fresh could resolve the problem.

Check the Filters pane for any filters that might affect the slicer and cause it to show only one value. Filters at the visual, page, or report level can sometimes conflict with slicer behaviour.

Kindly refer to the below following links for better understanding:
Using slicers in the Power BI service - Power BI | Microsoft Learn

Slicers in Power BI - Power BI | Microsoft Learn

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.

[Visharavana · Accepted solution]

Hi @Anonymous 
You can start by examining slicer interaction. For example, if you have three slicers, the first slicer has filtered some values in the other two.

[Cookistador]

Hi @Anonymous 

It looks like that your slicer keeps slicers from your other reprots

Can you make the following check

• Select the problematic slicer in your new report.
• Go to the "Visualizations" pane.
• Look for the "Filters on this visual" section.
• If there are any filters applied to the field used in the slicer, click the "Clear filter" (eraser) icon next to them.

Can you also have a look on the slicer applied on your visual (for example comming from anothe element)

If it is just a simple slicer, what I generally do, I delete the slicer and create a new one