Disconnected Table-Multiple slicers not syncing

Hi Subash2345,

This behavior happens because your disconnected table is only partially mapped to the model logic. While the Month slicer works through explicit DAX logic, the Financial Year slicer is not synchronized because there is no shared filtering mechanism enforcing both dimensions together when using a disconnected table.

To keep Financial Year and Month in sync, both must be handled explicitly in DAX. The correct approach is to capture both slicer selections from the DummyDate table and apply them to the Date table using TREATAS. Your YTD logic is conceptually correct, but it should enforce the Financial Year filter and the Month boundary together within the same evaluation context to avoid mismatches across visuals.

Key point:
When using disconnected tables, slicers never synchronize automatically — every slicer dimension (Financial Year, Month, etc.) must be explicitly applied in DAX using TREATAS or equivalent filter logic.

Helpful sources:

Disconnected tables and TREATAS

https://learn.microsoft.com/power-bi/transform-model/desktop-relationships-understand 

https://learn.microsoft.com/dax/treatas-function-dax 

Time intelligence and custom fiscal calendars

https://learn.microsoft.com/dax/time-intelligence-functions-dax 

Microsoft Learn (recommended):

https://learn.microsoft.com/training/modules/dax-power-bi-time-intelligence/ 

Savio Ferraz | Microsoft Ambassador Edurocks and MinecraftEdu | Microsoft Learning Consulting | Google Certified Trainer and GEG Leader

Did my answer help? Mark my post as a solution or like it if you found it useful.

Hi Subash2345 ,

To ensure consistency across all metrics (YTD Target, YTD Performance, Actual vs Target, YoY Variance, MTD, and the line chart), it's important to note that a disconnected table does not automatically propagate filters. The Month slicer functions only because it is explicitly handled in DAX, while the Financial Year slicer does not sync for the same reason, it isn't applied in every measure.

When using a disconnected DummyDate, both the Financial Year and Month slicers must be manually incorporated into each measure. This means each metric should:

Retrieve the selected Financial Year from DummyDate

Retrieve the selected Month in FY order

Apply both selections to the actual DateTable within the same evaluation context

Applying this approach consistently ensures all visuals respond the same way. For example, selecting November will always evaluate from July to November of the chosen Financial Year in both tables and charts.

Your current YTD logic is on the right track, as it applies the Month boundary. However, to achieve full synchronization, the Financial Year selection must also be included with the Month logic in every measure. If any metric omits one, that visual will become unsynchronized.

The solution is measure-driven, not specific to visuals. By standardizing FY and Month handling across all metrics, both slicers will function as if they are connected, even though the table remains disconnected.

Thank you and Continue Using Microsoft Fabric Community Forum.