DAX

Hi baxidor​,

Yes, you can keep this measure-based, but I would change one part of the design: don't use the original FactTable[EndDate] column directly on the X-axis.

A measure can change the value returned for a date, but it cannot move a row from one X-axis category to another. If the axis is FactTable[EndDate], Power BI has already grouped the rows by that original date before your measure is evaluated.

I would use a Date table (or a disconnected copy of your Date table) on the X-axis and let the measure calculate the effective end date for each lot.

Conceptually:

The important part is that 'Axis Date'[Date] is what drives the visual rather than FactTable[EndDate].

Your measure then decides:

original end date for the normal scenarios

OR

shifted working-day end date for Scenario C

That way the value can appear against the shifted date without storing a calculated Final End Date in the fact table.

Microsoft's documentation on model relationships and filter propagation explains why the original date field on the axis continues to filter the fact rows, and their date-table guidance covers the normal pattern of using a dedicated date table for grouping dates.

If you share the exact 5-working-day shift logic from the old calculated Final End Date, that part can then be moved into EffectiveEndDate in the measure.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.