Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
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
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
42 | |
21 | |
21 | |
14 | |
13 |
User | Count |
---|---|
43 | |
39 | |
33 | |
18 | |
17 |