Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
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
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.