Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
Hello,
Can some one explain this ;
= Table.TransformColumns( Source,
{ "Date", each Date.From(_) } which does what it say "date" now = a date ;
but if I dispense with the full syntax
= Table.TransformColumns( Source,
{ "Date", Date.From } )I now also transforms the date type ? which is useful, just wondered why ?
Richard.
Solved! Go to Solution.
Hi @Dicken
I think it's the behavior of Table.TransformColumns. If you see
Table.TransformColumns - Table Function | Power Query M
this function decides how to apply the transformation function to each value or whether to update the column type metadata.
In { "Date", each Date.From(_) }, Table.TransformColumns only sees a custom lambda, “(x) => Date.From(x)”. It doesn’t know the return type of this lambda, so it leaves the column type metadata unchanged.
While in { "Date", Date.From }, Table.TransformColumns sees a native function that has a declared return type in the M library (type date). Since it knows that return type, it sets the column’s metadata to date as well.
Ran a simple test below,
let
Query1 =
let
Source = #table(type table [Date = text], {{"2025-08-22"}}),
Transform1 = Table.TransformColumns(Source, {"Date", each Date.From(_)}),
Transform2 = Table.TransformColumns(Source, {"Date", Date.From})
in
{ Transform1, Transform2 }
in
Query1Hi @Dicken
I think it's the behavior of Table.TransformColumns. If you see
Table.TransformColumns - Table Function | Power Query M
this function decides how to apply the transformation function to each value or whether to update the column type metadata.
In { "Date", each Date.From(_) }, Table.TransformColumns only sees a custom lambda, “(x) => Date.From(x)”. It doesn’t know the return type of this lambda, so it leaves the column type metadata unchanged.
While in { "Date", Date.From }, Table.TransformColumns sees a native function that has a declared return type in the M library (type date). Since it knows that return type, it sets the column’s metadata to date as well.
Ran a simple test below,
let
Query1 =
let
Source = #table(type table [Date = text], {{"2025-08-22"}}),
Transform1 = Table.TransformColumns(Source, {"Date", each Date.From(_)}),
Transform2 = Table.TransformColumns(Source, {"Date", Date.From})
in
{ Transform1, Transform2 }
in
Query1Thanks ,
RD
(_) as date => Date.From(_)
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |