Discrepancy in Dual-Visual Comparison (Peer Analysis) despite identical Slicer selections

[AlonCarmel]

Scenario: I have a Power BI report designed for financial peer comparison (CSM Amortization). The report is split into two identical sections (Top and Bottom) to allow users to compare two different companies or scenarios side-by-side.

The Setup:

• Visuals: Waterfall charts showing "Amortization Amounts" and "Amortization Percentage".

• Measures: Using dynamic DAX measures with SWITCH and SELECTEDVALUE to toggle between "Incremental" (Raw SUM) and "Cumulative" (Running Total based on an Index column).

• Slicers: Both sections have an identical set of slicers: Year, Segment, Company, and Type (Cumulative/Incremental).

• Interactions: "Edit Interactions" is configured so the Top slicers only affect the Top visuals, and Bottom slicers only affect the Bottom visuals.

• Button: There is no hidden button or something.

The Problem: When I select the exact same filters for both the Top and Bottom sections (same Year, same Company, same Segment), the visuals display different values.

• The Bottom visual shows correct figures (e.g., Total ~247M in "Up to 1 Year").

• The Top visual shows incorrect, significantly lower figures (e.g., Total ~1,172M in "Up to 1 Year").

What I've Checked:

1. Visual-Level Filters: Confirmed there are no hidden filters applied to the specific bottom visuals.

2. Measures: Both sections use the same DAX measures.

3. Data Source: Both visuals point to the same Fact table (DB).

Interactions: Confirmed there is no "cross-talk" where the top slicers are filtering the bottom section.

My Question:
What could cause this discrepancy? Could it be a "Filter Context" leakage or an issue with how ALLSELECTED behaves when the same table is filtered by two different sets of disconnected slicers? How can I ensure that both sections calculate the values identically?

[AlonCarmel]

Update on the issue: I've discovered that the discrepancy disappears when I disable "Single Select" and turn off "Force Selection" on the slicer (a toggle between "Health" and "LTS").

When "Single Select" is ON, the bottom visual displays incorrect totals. When I allow multiple selections (even if only one is practically selected) or use a regular slicer, the values align perfectly.

It seems like the ALLSELECTED function in my DAX measure is interacting poorly with the Required Single Selection state of the slicer, causing a filter context conflict in the cumulative calculation