Forum Discussion
Issue with Left Anti Join - Type Text
- 5 years ago
Hey Anonymous - I'm not convinced the join has anything to do with it. Here is what could have happened:
- You are converting some field to numerical of some sort (whole number, currency, percentage, whatever)
- Way WAY below the 1,000 records Power Query uses for caching is a text value in that field.
- When you do the merge and expand the table, now that record that might be record 30,000 is now record number 200. Now Power Query will try to convert it to a number and it breaks.
So look carefully at all numeric fields.
A quick way to do this is to load both tables into Power BI as a test. That will load all records. Power BI will give you a good clean error on the numeric field with an alpha in it.
Or, you can try to use the Table.Profile() function on each table. Just wrap the last line of each table with Table.Profile() in the formula bar and wait. See if anything odd shows up.
Thanks, it turns out there was a single rogue entry in the supplier number column. All sorted now!
Great Anonymous - glad you got it figured out. Sometimes weird issues can stay hidden until something else causes them to manifest. I've seen issues remain hidden after dozens of transformations, then a merge or group by will suddenly blow up and the cause was 10 steps earlier in the process.