Forum Discussion

Syndicate_Admin's avatar
Syndicate_Admin
Icon for Administrator rankAdministrator
1 year ago
Solved

Sync Segmentation without the need to include filters

Nice day I have the following question I have a multi-page model, in this there is a main page with slicers and tables, I want to include a button that redirects me to a page with the details of th...
  • v-hashadapu's avatar
    1 year ago

    Hi Syndicate_Admin , Thank you for reaching out to the Microsoft Community Forum.

     

    You can use Sync Slicers combined with Page Navigation buttons. On your main page, place your slicers and visuals. These slicers will drive the filtering logic. Then, create a details page with the same data model fields used in the visuals but exclude the slicers to keep it clean for presentation or export. To retain the slicer filtering across pages, use the Sync Slicers feature. Select each slicer on the main page, go to the View tab and open Sync Slicers. In the pane, enable sync for the details page but uncheck the Visible option to keep the slicer hidden there. This ensures that the slicer filters still apply, even though they’re not shown.

     

    Next, insert a button on the main page via Insert -> Buttons -> Blank, then enable Action in the Format pane. Set the action type to Page navigation and choose your details page as the target. Clicking this button will take users to the details page while preserving the slicer context.

     

    You can also use visual calculations for dynamic metrics on the details page (via the Modeling tab) and leverage Power BI Service export options for screenshots. These include Export to PDF, PowerPoint or even automated export via Power Automate, which now supports capturing filtered visuals as images.

     

    To export cleanly, use Reading View or adjust page settings under View -> Page View -> Fit to Page. Be sure to test the button navigation and filter propagation to ensure everything reflects the expected state. If filters don’t sync as expected, verify your data model relationships or consider using report-level filters as a fallback.

     

    If this helped solve the issue, please consider marking it “Accept as Solution” and giving a ‘Kudos’ so others with similar queries may find it more easily. If not, please share the details, always happy to help.
    Thank you.