The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hello to all,
I wrote the code below in Dax.do
EVALUATE
VAR CustMinDate =
ADDCOLUMNS (
VALUES ( Customer[CustomerKey] ),
"@MinDate", FORMAT ( CALCULATE ( MIN ( Sales[Order Date] ) ), "dd/mm/yyyy" ) & "" //here data linage must break
)
VAR CustMinDateSales =
ADDCOLUMNS (
custMinDate,
"FirstSales", [Sales Amount]
)
RETURN
TOPN ( 10, CustMinDateSales )
ORDER BY [@minDate] DESC
and the result is:
Why is this happening???
Solved! Go to Solution.
Hi @sokg
The columns added by ADDCOLUMNS will never preserve data lineage, regardless of the expression used.
However, columns of the first argument of ADDCOLUMNS will preserve lineage.
In your example, the lineage of Customer[Customer Key] is preserved, so the values returned in the "FirstSales" column are [Sales Amount] filtered by each row's Customer Key, but with no other filters.
Regards,
Owen
Hi @sokg
The columns added by ADDCOLUMNS will never preserve data lineage, regardless of the expression used.
However, columns of the first argument of ADDCOLUMNS will preserve lineage.
In your example, the lineage of Customer[Customer Key] is preserved, so the values returned in the "FirstSales" column are [Sales Amount] filtered by each row's Customer Key, but with no other filters.
Regards,
Owen