Filters not works while selecting multiple Period

Hello my friend,

The issue is that SELECTEDVALUE returns BLANK when multiple rows are selected for EQ and LY — it only works with a single value. You need VALUES or just remove those vars and let the filter context handle it naturally.
Also, your LatestQuarterNumInLatestYear is getting the latest month number across all selected quarters, but filtering on 'Fact table'[Month Number] directly — make sure that column exists and matches.
Try this cleaner version:
daxTotal Value =
VAR LatestYYYYQQ =
CALCULATE(
MAX('Calendar'[YYYY-QQ]),
ALLSELECTED('Calendar'[YYYY-QQ])
)
VAR LatestMonth =
CALCULATE(
MAX('Calendar'[Month Number]),
ALLSELECTED('Calendar'),
'Calendar'[YYYY-QQ] = LatestYYYYQQ
)
RETURN
CALCULATE(
SUM('Fact table'[amount]),
'Fact table'[Quarter] = LatestYYYYQQ,
'Fact table'[Month Number] = LatestMonth
)
The key changes: dropped SELECTEDVALUE for EQ and LY (let the visual's row context filter those naturally), and simplified the latest quarter/month logic into two clean vars. If EQ and LY still need explicit filtering, share what Table2 is — it looks like a disconnected table which would explain why SELECTEDVALUE was breaking things.

Hi Anonymous

In your scenario, when several Years and Quarters are selected, the visual should always resolve to:
the latest selected Year,
the latest Quarter within that Year, and
the latest Month within that Quarter,
and then compute the measure only for that specific combination.
The most reliable approach is to:
Determine the latest Year in the current filter context.
Determine the latest Quarter within that Year.
Determine the latest Month within that Year–Quarter.
Apply these three values as filters when calculating the measure.
A revised version of the measure that follows this pattern is shown below.

Total Value =
VAR LatestYear =
CALCULATE(
MAX ( 'Calendar'[Year] ),
ALLSELECTED ( 'Calendar' )
)

VAR LatestQuarter =
CALCULATE(
MAX ( 'Calendar'[Quarter Number] ),
ALLSELECTED ( 'Calendar' ),
'Calendar'[Year] = LatestYear
)

VAR LatestMonth =
CALCULATE(
MAX ( 'Calendar'[Month Number] ),
ALLSELECTED ( 'Calendar' ),
'Calendar'[Year] = LatestYear,
'Calendar'[Quarter Number] = LatestQuarter
)

VAR _EQ = SELECTEDVALUE ( 'Table2'[EQ] )
VAR _LY = SELECTEDVALUE ( 'Table2'[LY] )

RETURN
CALCULATE(
SUM ( 'Fact table'[Amount] ),
KEEPFILTERS ( 'Calendar'[Year] = LatestYear ),
KEEPFILTERS ( 'Calendar'[Quarter Number] = LatestQuarter ),
KEEPFILTERS ( 'Calendar'[Month Number] = LatestMonth ),
'Fact table'[EQ] = _EQ,
'Fact table'[LY] = _LY
)

Why this approach is more robust
Avoids relying on SELECTEDVALUE for Calendar fields
When multiple Years or Quarters are selected, SELECTEDVALUE for those columns returns BLANK, which breaks the logic. Using MAX over ALLSELECTED explicitly identifies the latest value within the current selection.
Uses ALLSELECTED over the Calendar table
ALLSELECTED('Calendar') considers only the periods that the user has chosen (including slicers and visual-level filters), but disregards row-level context in the visual, making it appropriate for computing “latest” values.
KEEPFILTERS preserves user context
By using KEEPFILTERS, we ensure that the measure does not remove other existing filters on the Calendar table, but rather narrows them down to the latest Year–Quarter–Month combination.
Always resolves to the most recent period
For a selection such as 2025‑Q4, 2026‑Q1, and 2026‑Q2 with Month 3 available in 2026‑Q2, the logic will correctly identify:
Year = 2026
Quarter = 2
Month = 3
and the measure will return values only for that final period.
If your Calendar table uses different column names (for example YYYY-QQ instead of Quarter Number), the same pattern applies; you would simply adapt the column references accordingly.

Hi,

Try this measure pattern

Last selected date = max(calendar[date])

Amount in last selected quarter = calculate(sum(Data[sales]),datesbetween(calendar[date],eomonth([Last selected date],-3)+1,[Last selected date]))

If this does not work, then share the download link of the PBI file.

Hi Anonymous 

Doesn't your fact table have dates. This would have been simpler if calculation is based on actual dates.