janwyl - Actually the example you gave almost proves to me that it's the sort collation sequence - the API is sorting the hyphen character differently than SnapLogic. One quick check you can perform is to Copy the stream and save the results after the API, then run the other side of the Copy through a Sort snap and save those results and compare for yourself.
The error I had was this :
importId is the value I have fetched from the API (in ascending order) and I am joining with other data using inner join and ascending sort order. I interpret this to mean that the error was thrown because the importId of 3210448-USM18 came before 3210448-NYR6 in the join.
I have just twice fetched only the importIds from the API (without doing the join) and both times 3210448-NYR6 came before 3210448-USM18.
In addition, every single value of importId takes the form of 7 numbers followed by a hyphen followed by some other combination of letters and characters. My understanding of sort collation may not be sufficiently advanced so apologies if I'm on the wrong track - given that format I'm not sure how sort collation could have an impact. Even if one collation ignores the hyphen it's the same for every single value?
Thanks again for your thoughts !
