topic Re: updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports in Developer

updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports

WellsFang — Wed, 01 Jul 2026 03:45:52 GMT

Hi Power BI Team,

We are experiencing an issue with Power BI Embedded where `updateSettings` does not update `panes.syncSlicers.visible` when the report is in View mode.

Our scenario is:

1. The report starts in View mode.
2. The user enters Edit mode.
3. We call `updateSettings` to show the Sync Slicers pane:

report.updateSettings({ panes: { syncSlicers: { visible: true } } });

This works as expected.

4. When the user exits Edit mode and the report returns to View mode, we call `updateSettings` again to hide the Sync Slicers pane:

report.updateSettings({ panes: { syncSlicers: { visible: false } } });

However, this does not work. The Sync Slicers pane remains visible.

After testing, it seems that `syncSlicers.visible` can only be toggled while the report is in Edit mode. In View mode, calling `updateSettings` with `syncSlicers.visible = false` has no effect.

Could you please confirm whether this is expected behavior or a bug?

If it is expected behavior, is there a supported way to hide the Sync Slicers pane after switching the embedded report from Edit mode back to View mode?

Thanks.

Re: updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports

Murtaza_Ghafoor — Tue, 07 Jul 2026 05:24:33 GMT

@WellsFang

Yes, this is expected behavior.

The Sync Slicers pane is an editing feature, and its visibility is only maintained while the report is in Edit mode.

Once the report goes back to View mode, report.updateSettings( ) does not control the prominence of the Sync Slicers pane.I hope this will clarify the situation.

If this helps, ✓ Mark as Kudos | Help Others

Re: updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports

v-csrikanth — Wed, 08 Jul 2026 09:20:48 GMT

Hi @WellsFang

This is consistent with how the Sync slicers pane behaves in the embed client SDK. Unlike filters or page Navigation(viewer-facing), sync slicers is an edit-mode authoring pane, so setting syncslicers.visible = false after returning to View mode has no effect — hence it stays "stuck."

Recommended workaround: Hide it while still in Edit mode, before switching to View:

----------------------------------------------------------
await report.updateSettings({
panes: { syncSlicers: { visible: false } }
});
await report.switchMode("view");

----------------------------------------------------------
Awaiting update settings before switch mode ensures the pane is hidden before the transition.
Alternatively, re-apply your full panes config as part of the mode-switch handler.

Thank you,
Srikanth Cheri
CST Team

Re: updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports

v-csrikanth — Mon, 13 Jul 2026 04:13:49 GMT

Hi @WellsFang
We would like to inquire whether have you got the chance to check the solutions above in commiunity to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

Re: updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports

v-csrikanth — Thu, 16 Jul 2026 12:39:26 GMT

Hi @WellsFang

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Thank you.

Re: updateSettings does not update syncSlicers.visible in View mode for Power BI Embedded reports

masonreed11t — Fri, 17 Jul 2026 10:00:10 GMT

This looks like an expected limitation with Embedded reports. The Sync Slicers pane is an Edit mode feature, and updateSettings may not apply pane visibility changes once the report is back in View mode.

You may need to hide it before switching modes or handle the mode transition logic differently. If the behavior is reproducible with the latest SDK, it would be worth opening a Microsoft support ticket to confirm whether this is a bug or an unsupported scenario.