1 of 1 people found this helpful
Looks like you've found a bug, and a good one at that. From our initial investigations, looks like we're not adding a collation to the generated columns like "Table Name", which is causing our joins to fail. I've opened a bug and assigned it out, so it will be fixed in a maintenance release.
In the meantime...are you in the 10.0 Beta? In the Beta, we coerce collations if they don't match for cross-database joins if each set of files comes from a different connection (a lot of jargon, but hopefully the snapshot helps). This could be a workaround while we fix the bug:
Note that I created one text connection for the left side of the join, and another for the right side. This will force collation coercion.
Please reach out if you need Beta access or have more questions.
-Roger and the Data Prep and Integration Team