Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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
User | Count |
---|---|
76 | |
75 | |
46 | |
31 | |
27 |
User | Count |
---|---|
99 | |
91 | |
51 | |
49 | |
46 |