Import Set API - "error" status in response instead of "Ignored" status for ignored rows

[Tom Sienkiewicz]

Hi, something weird is happening with in the response.

We're trying to use an import set table, which is linked to 3 transform maps and 3 target tables. The transform maps have an onBefore script, which depending on the condition, ignores the specific row. The problem is that this actually returns the "Error" status in the response message for that object, instead of the "Ignored" status which I would expect to have:

<response>
<import_set>ISET6182655</import_set>
<staging_table>u_import_contract</staging_table>
<result>
<error_message>Target record not found</error_message>
<status_message>Row transform ignored by onBefore script</status_message>
<transform_map>Import Agreement Line</transform_map>
<table>u_agreement_line</table>
<status>error</status>
</result>
</response>

We're not setting any errors in the onBefore, just setting:

ignore = true;
status_message = "test";

It seems to me like it is trying to perform the fields mapping/coalescing even though the onBefore tells it to ignore the row. Is this normal? Or is this a known issue with this API perhaps?

Am a little confused here, thanks in advance for any help.

[Periyasamy P]

If you set ignore=true in your onbefore script, then system automatically add this error message "Row transform ignored by onBefore script".

So this is expected one.

[Tom Sienkiewicz]

Hi, thanks for your update, but that one is not an error message, it is a status mesage. And the response also has a possible status value being <status>ignored</status>... 

so I'm not sure this is the way it should really behave?

I am not worried about the "status_message" - but if the other system gets a "status" being an error where we simply ignore a row on our side, that makes it a problem from error handling perspective.