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!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
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
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 20 | |
| 11 | |
| 10 | |
| 4 | |
| 4 |
| User | Count |
|---|---|
| 34 | |
| 30 | |
| 19 | |
| 12 | |
| 11 |