Transform Map: Ignored Row Still Inserts Target Record

[JosephW1]

Hello,

First, I will establish some basics that are probably floating to the top of your mind:
1. The transform map is setting ignore to true when action == "insert".
2. If I look in the Import Set Row [sys_import_set_row] table for row 42,052, its State is "Ignored".
3. If I look in the Transform History for the given transform, the ignore count is 25k+.
Points 1-3 should help establish that this isn't a "Please teach how to ignore an import set row" question, as the ignore feature is already in use as shown by the transform history, but this is rather a troubleshooting-assistance question.
4. However, if I go to the target table, there is a record there that A) matches up to the Import Set Row 42,052 mentioned earlier, B) was created by the unique user that runs the transform, C) was created during the transform's execution, and D) was created at the exact moment that the Import Set Row was updated(!).
5. In the target table I can find similar ignored-yet-inserted target records dating back to late Feb 2022, but none before that point. The table dates further back than Feb 2022, so this likely indicates the onset of this symptom.

I haven't yet identified any relevant changes in our environment that occurred in late Feb 2022, nor have I yet found any documentation on what to do when inserts circumvent the ignore mechanism like this, so that's why I'm bringing this question here.

To date, here is where I've looked for the culprit:

1. GlideRecord.updates in transform map field maps or transform scripts. Nope. -Thanks @palanikumar 
2. GlideRecord.updates in BRs/script includes that could be triggered by this transform map. Nope

Any ideas on what is causing this malfunction, please? Thanks!

Kind Regards,
Joseph

[palanikumar · Accepted solution]

Hi,

Check whether any transform script or field mapping script updating the record.

Thank you,

Palani

[palanikumar]

Hi @JosephW 

Is your issue resolved? If yes then mark my response as correct answer and close the thread.

Thank you,

Palani

[JosephW1]

I eventually found a gr.update() in an onAfter script that we've had in place for years. I don't know why it only just recently started producing this symptom, but disabling the update on ignored rows eliminated the symptom. Thanks!

[JosephW1]

There were no GlideRecord.update()s in this transform map's field map scripts or transform scripts.

Any other ideas, please? Thanks!