Transform map showing updated records as ignored

[JJG_SNOW]

I have a transform map that is updating many records, but when I check the transform history it shows the records as ignored. I am %100 certain that records are indeed being updated, I have confirmed it several times. 

What could cause the records to be showed as ignored when they have been updated?

The target table is the cmdb_ci_computer table.

There are several onAfter transform scripts, but they are very simple and all follow the same general format.

Example:

if (source.u_asset_tag.toLowerCase().indexOf("undefined") < 0) {
        target.asset_tag = source.u_asset_tag;
        target.update();
    }

[Tony Chatfield1 · Accepted solution]

Hi, you see ignored records as there are no field differences between the source and target data and so the import rows are 'ignored'. However, transform scripts are making changes and so you see the target record as updated.

One thing to note; based on the code you have posted I think the transform script would be better suited as a 'before' transform script. As in the current configuration if any field on the record is changed during the import process (the record is updated) this transform script will result in a second save\update of the record when it runs, and this 'double tap' is normally considered inefficient and undesirable.

[G24]

In my case all of the values are identical, so the Transform is marking all rows as "Ignored", however two of my Field Maps involve script and I need them to run.

Is there any way to "Force" the transform to process rows, even if it "thinks" they may be ignored?

[G24]

Answering my own question (sort of) here, you can force the transform to run by mapping a new field.  If you may the Updated field to any field OTHER than Updated, that should cause the transform to always process rows and never ignore them.  I think.

[Sumanth16]

Hi John,

Is there any comment (or) error message added on the import set of that transform history?

Thanks & Regards,
Sumanth Meda