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
In Excel PQ, Table.AddColumn(.., .., each _text expression_), type number) doesn't convert text expression to number, while the header of the column shows that it has a numeric type. And, if you merge a table with such a column with a table with "pure" numeric column, UI doesn't prevent from doing that, and at the same time the merging provides only nulls in the "right" table for left-outer joins.
So there is the issue is that the type of a column is numeric, and values kept it it are text. That doesn't seem to be logical, and cirtain checks doesn't perfrorm properly, as described above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.