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!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I am curious to know if this is expected behavior in Power Query.
I have a couple of columns that are Lat/Long, which I transformed all null values to be zero. Then, I added a Custom column to calculate Radians on those columns.
I came up with nulls trying to add another Custom column and started stepping through it and discovered that values previously changed from null to zero had reverted back to null.
Is this normal?
Here is the snippet that is giving me grief. There is nothing special before or after. I removed some columns before this and changed some types after.
#"Replaced Value - nulls" = Table.ReplaceValue(#"Filtered Rows",null,0,Replacer.ReplaceValue,{"USERLong", "USERLat", "LOCLat", "LOCLong"}),
#"Added Custom UserLatRad" = Table.AddColumn(#"Renamed Columns", "USERLatRad", each (Number.PI/180)*[USERLat])
If it makes a difference, the transformations on this table are coming from a merge of 3 different tables that orginiate in API.
Solved! Go to Solution.
The table argument of your Table.AddColumn function is referring to the wrong table.
Probably it should read
#"Added Custom UserLatRad" = Table.AddColumn(#"Replaced Value", ...
@ronrsnfld ... Thank you! Copied those steps in from another space I had been working in, and never even considered that. That fixed it! Appreciate the help.
The table argument of your Table.AddColumn function is referring to the wrong table.
Probably it should read
#"Added Custom UserLatRad" = Table.AddColumn(#"Replaced Value", ...