Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Can anyone see why the following fails to change the data lineage from dimdate[date] to bookings[agreement end date]?
Book AvailToRenew=
VAR _MyTable =
ADDCOLUMNS (
SUMMARIZE('Bookings', 'Bookings'[Deal ID]),
"@ATR", sum('Bookings'[Contract Value])
VAR _Dates = VALUES('Bookings'[agreement end date])
RETURN
CALCULATE(
SUMX(_MyTable, [@ATR]),
TREATAS(_Dates, DimDate[Date])
)
2 notes
(1) if I make the TREATAS in a separate measure, the date shift holds. Ther must be something in the virtual table where I'm failing to shift the lineage.
(2) I am having the same issue on similar constructs as the above using USERELATIONSHIP and a physical table relationship.
@charleshale , In this case date table should not be joined with any date of your table
example
CALCULATE(
sum('Bookings'[Contract Value]),
TREATAS(VALUES('Bookings'[agreement end date])
, DimDate[Date])
)
In case of multiple relationship
CALCULATE(
sum('Bookings'[Contract Value]),
UseRelationship([agreement end date], DimDate[Date])
)
Not sure on role of id in this case, As it is sum
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!