Sync slicers with different datasets in power bi on different pages

[Renukam]

I have a Power BI report where different pages use different datasets. All datasets share a common field (Dashboard_Type ). Requirement is to retain the slicer selection (e.g., Type1, Type2, Type3) when navigating between pages. Since Sync Slicers and Page Navigation don’t work across datasets, is there any supported way in Fabric/Power BI to persist or synchronize slicer selections across pages using different datasets, without consolidating into a single dataset?

[v-lgarikapat]

Hi @Renukam ,Thank you for reaching out to the Fabric Community Forum.

@dk_dk , @cengizhanarslan Thanks for your prompt response.

 Hi @Renukam I wanted to follow up to check if you had a chance to review the information provided by @dk_dk  and @cengizhanarslan  . If you are still facing issues, please don’t hesitate to reach out  we’ll be more than happy to assist you.

Best Regards,

Lakshmi.

[v-lgarikapat]

Hi @Renukam ,

We haven’t heard back from you regarding our last response, so I just wanted to check in to see if you were able to resolve the issue. If you have any further questions or need assistance, please feel free to let us know.

Best Regards,

Lakshmi

[dk_dk]

Hi @Renukam 

You could create a "filter" table that has a single column with all possible values of "Dashboard_Type" (across both datasets). You can do it manually or via DAX like so:

DashboardTypeFilter = DISTINCT(UNION(DISTINCT(DatasetA[DashboardType]),DISTINCT(DatasetB[DashboardType])))

Then configure relationships:

And finally, only use the DashboardType column from the DashboardTypeFilter table in your slicers. You will be able to sync slicers across pages and filter the two disconnected datasets with the same slicer.

Hope this helps. Let me know if you have any questions.

[Renukam]

Hi,
values are common in all fact tables in Dashboard Type column. There are 3 same values for all the fact tables.
so I've created 

Dashboard Type common = DATATABLE("DASHBOARD_TYPE",STRING,

{

    {"Type1"},

    {"Type2"},

    {"Type3"}

})
and then established relationship between this dim table and all other fact tables.

But it is wrongly filtering the data when I'm using DASHBOARD_TYPE from dim table in slicer.

[dk_dk · Accepted solution]

Hi @Renukam 

Can you send a screenshot of your model view, with the Dashboard Type common table and its relationships to your fact tables?

It should look something like this:

with one to many relationship.

[cengizhanarslan]

Option 1) Single dataset via shared dimensions

If the requirement is true filter persistence, this is the only native solution:

• Create a shared dimension (e.g. DimDashboardType)

• Use one semantic model

• Connect all pages to that model

This can still be modular:

• Multiple fact tables

• Subject-area–specific pages

• Role-based visibility

 

Option 2) Composite model (DirectQuery to Power BI dataset)

If consolidation is not possible:

• Pick one dataset as the core

• Other datasets are accessed via DirectQuery to Power BI dataset

• Arrange relationships

• Pages use the composite model

This allows:

• One slicer

• One filter context

• Multiple data sources behind the scenes

Tradeoffs:

• Performance

• More complexity

[Renukam]

Hi Cengizhanarslan,
Regarding Option 1

Thank you for your response, I created a common dimension table and established relationship between this dimension table and other Fact tables, but it is taking cartesian product and while filtering via slicer in which column from dim table is used, it is wrongly filtering the data.