Fabric is Generally Available. Browse Fabric Presentations. Work towards your Fabric certification with the Cloud Skills Challenge.
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
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.