Slicer (new) not in sync when using Page Navigator

[rdeman]

Hi all,

I've been trying out the new slicer, and although it remains in sync nicely across pages (unlike this topic), the sync breaks whenever using the Page Navigator; all selections are reset when changing pages through the button navigator. 

Anyone else noticed that? Is something wrong with my setup or is the new slicer not yet set up for use with the page navigator? 

Thanks! 

~R

[ndlofnsd]

I have the same problem... When using the "page navigation" buttons, the new button slicer gets reset.. Very annoying ☹️

[rdeman]

Hi @v-jiewu-msft ,
Thanks for your reply. 
Yes, all slicers are in sync (and the sync is working, because the sync works when changing pages at the bottom). 

I assume the page navigator is set up correctly, because other functionalities work. I've tried setting it up on a new / more or less blanc report and I have the same issue there.

Yes, PBI Desktop is up-to-date (2.124.1554.0). 

Have you tried the functionality yourself? 

Just to clarify: The issue is that all new slicers are reset when using the page navigator, even though the slicers are supposed to remain in sync. 
Using the Slicer (new):

[v-jiewu-msft]

Hi @rdeman ,

If I understand correctly, the issue is that the sync slivers break when you were using the Page Navigator. Please try the following methods and check if they can solve your problem:

1.Go to the View tab in Power BI Desktop, click Sync slicers, and make sure that the slicers are checked for each page you want them to sync on.

2.Double-check that the Page Navigator is set up correctly

3.Ensure that you are using the latest version of Power BI Desktop.

Looking forward to your reply.

Best Regards

[AntonBaton]

I have the same issue:

when I use my droll-though page and later return to the original page with the Back button, the SLICER NEW is reset. All other slicers are trill in place. What is more, if I just change the slicer new to the original slicer with the same data and settings - the original slicer works normally, keeping its value when returning from drill-through.

I think this is a bug with slicer new and it should be reported.