Slicer-New issue in PBI embedded in Power Point

[dreamyMath]

Hi all, I just encoutered this issue today or few days ago. While the server version funtions well. The embedded pbi in power bi, especially the button using "Slicer-New" seem to be verry inresponsive. Please please help me look ino the matter. Many thanks

For example: my report relies on multiple slicers that we have both new and old one. The new button when clicked should be bolded and greyed in indicating selection and pie chart updates accordingly. But recently it doesn show as such and only get updated/refreshed when I go ahead and change my slicer-old filter.

can you take a look into the matter, for example here is a starting view, you see the old and new are selected and highlighted:

But when i click on the % button below, say 15%, then the button doesn update:

Until I have to hit the slicer old above, only then the visual of the new slicer s updated:

[Poojara_D12]

Hi @dreamyMath 

From your screenshots and description, it looks like the issue is specific to the “Slicer – New” visual style in Power BI Embedded, where the button selection (like 15%, 20%, etc.) is not visually updating as expected. Normally, when you click a button in the new slicer style, it should highlight (bold/greyed) immediately and trigger a refresh of the connected visuals (like your pie chart). However, in your case, the slicer’s state doesn’t visually update until you interact with the old slicer above it. This behavior suggests that there may be a rendering or interaction bug in the embedded Power BI environment that doesn’t exist in the Power BI Service (server version), where it works normally.

In other words, the slicer selections are actually being applied in the background, but the UI does not reflect the change until another action forces a refresh. This explains why clicking the old slicer makes the new slicer buttons update. It could be related to a recent Power BI update, or an incompatibility between slicer types when used together in embedded mode. A workaround for now would be to avoid mixing the new and old slicer types in the same report, or to trigger a page refresh/programmatic refresh via the Power BI Embedded JavaScript API after a new slicer selection.

A good starting point for troubleshooting this issue is to first confirm whether the problem is tied to the browser or embedding environment. Try opening the same embedded report in different browsers (Chrome, Edge, Firefox) and clearing cache to see if the slicer-new buttons behave differently. Next, check that your Power BI Embedded environment and the Power BI JavaScript client library are updated, since UI rendering issues can occur when the embedded SDK is out of sync with the service updates. It’s also worth testing whether the issue reproduces when only slicer-new visuals are used, as mixing old and new slicers in the same page may be causing dependency conflicts. If it works fine with only new slicers, you could consider replacing the old slicers completely. Additionally, enabling cross-filter interactions explicitly between the slicer-new and visuals may help enforce updates. As a workaround, you could use the Power BI JavaScript API’s report.on('dataSelected') or report.refresh() event handlers to force a refresh of visuals after slicer interaction. Finally, if the behavior persists, capturing the Activity ID from the embedded session and raising a support ticket with Microsoft would be recommended, as this may be tied to a recent change in how slicer-new is rendered in embedded mode.

[v-sgandrathi]

Hi @dreamyMath,

Thank you @Shahid12523 for your response to the query.

Thank you for providing the additional information and confirming that the issue remains after re-embedding and testing on various machines. Your validation suggests that the problem is related to the new slicer behavior within the embedded Power BI in PowerPoint environment.

Since the slicer functions correctly in the Power BI Service but not when embedded, this points to a potential compatibility or rendering issue on the embedded side.

Given these findings, I recommend submitting a support ticket to Microsoft, as this appears to be a regression impacting multiple users.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you and continue using Microsoft Fabric Community Forum.

[v-sgandrathi]

Hi @dreamyMath,

We’d like to follow up on your support ticket. Has the issue been successfully addressed?

If a solution was provided, we’d truly appreciate it if you could share your experience or any relevant details, your input could be valuable to other community members.

Thanks again for being an active part of the Microsoft Fabric Community!

[dreamyMath]

Hi @v-sgandrathi, @Shahid12523,

many thanks for your suggestion. I confirmed that it seems to work again over the weekend... on speed of the refreshing visual Im still need to further test on the topic, cause i feel it s a little slower than usual. But we have tried with various alternatives also, maybe helpful for everyone:

we use chiclet filter as subsitute
switch back to version of old filter version

many thanks guys. 

[v-sgandrathi]

Hi @dreamyMath,

I'm glad you found a solution and resloved  the query. Thank you very much for sharing here.

If you have further queries please reach out.

Thankyou for connecting with Microsoft Community Forum.

[Shahid12523]

Issue: In Power BI embedded in PowerPoint, the “Slicer-New” button doesn’t visually update or trigger chart refresh unless “Slicer-Old” is clicked.
Cause: Likely a sync or interaction bug in the embedded environment—event propagation or slicer state isn't committing properly.
Fixes to try:
- Re-embed the report in PowerPoint.
- Check slicer sync and visual interactions in Power BI Desktop.
- Test behavior in Power BI Service to isolate the issue.
- Use bookmarks or default slicers as a workaround.

[dreamyMath]

Thank Shahed, 

yes we have isolated the issue by switching back to the old version to check, there the slicer will work properly. 

re-embedding/clear cache doesnt solve the problem. we also tested on different users PC

I have also tested on a much simpler report with the slicer new. there the visual lagging problem persist. so my guess is the bug in embedded env particularly on this new slicer... I hope MS teams can look into the matter, since Powerpoint are heavily used everywhere. 

thanks,
An