Joiner BUG

Hello, try delete rows at first file.

I have deleted all lines from the first file and I've go the same error message as you.

Basically we are joining empty file with empty file here which completely pointless exercise.

So I was wandering what kind of result do you expect?

Perfect! What I wanted to highlight is the abort behavior that occurs when there are no input rows. We have robots that compare records in files using a Joiner in other ETLs, and the Joiner has been throwing this error when there are no records to compare. What we expect is: a writer with 0 rows, not an aborted transformation.

In this other comparison robot, there are 2 readers, and if either side is empty, it throws an error upon failing to find the key. This behavior has emerged in recent versions.

Thank you for the clarification.

We did send you email last month did you see it?
 

Hi Mike, I received emails regarding the Python DLL and Joiner forums, as well as an email about the Capterra review.

Can try the following please.

Install latest version.
Double click on joiner object.
Click OK.
Run the transformation.

Please let us know the outcome