SFDC sparse lookup with upstream Transformer.
Posted: Wed Mar 01, 2017 9:34 am
While performing SFDC sparse lookup, the position of the lookup column in the input link is entered in SOQL's WHERE clause (counting from zero) e.g. ''{3}'' for 4th column.
If any column is modified/manipulated in a transformer (prior to SFDC stage) then modified column(s) move up in internal output from transformer (though not in Designer canvas), so when it comes to column position 'what you see is Not what you get'! This makes developing code with SFDC sparse lookup quite challenging.
Further, an unrelated/passthru column change (during post production maintenance) in an upstream transformer will necessitate modification of SFDC sparse lookup's WHERE clause to map to new position of lookup column.
Please share your thoughts/experiences on working around this issue.
If any column is modified/manipulated in a transformer (prior to SFDC stage) then modified column(s) move up in internal output from transformer (though not in Designer canvas), so when it comes to column position 'what you see is Not what you get'! This makes developing code with SFDC sparse lookup quite challenging.
Further, an unrelated/passthru column change (during post production maintenance) in an upstream transformer will necessitate modification of SFDC sparse lookup's WHERE clause to map to new position of lookup column.
Please share your thoughts/experiences on working around this issue.