Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Dicken
Continued Contributor
Continued Contributor

Transform Column / Type



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.

1 ACCEPTED SOLUTION
MasonMA
Community Champion
Community Champion

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
    Query1

MasonMA_1-1755879371212.pngMasonMA_0-1755879344613.png

View solution in original post

3 REPLIES 3
MasonMA
Community Champion
Community Champion

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
    Query1

MasonMA_1-1755879371212.pngMasonMA_0-1755879344613.png

Dicken
Continued Contributor
Continued Contributor

Thanks ,  

RD

(_) as date => Date.From(_)

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.