When a record is updated during a transform, and the next record is skipped because the value on the source for a coalesce field is null, the skipped record incorrectly has the target of the previous record.

Steps to Reproduce

  1. Get 3 incident record sys_ids from the instance on which you are reproducing the issue.
  2. Download the attached data.xls file.
  3. In the data.xls file, update rows 2,4, and 6 with the sys_ids from step 1.
  4. Create an import set using the data.xls file.
  5. After data is loaded, click on Create transform map.
  6. Give the map a name.
  7. Set target table as incident.
  8. Click Submit.
  9. Add two field maps to the transform:
    1. source field "u_comments" -> target "Comments", coalesce = false
    2. source script -> target sys_id, coalesce = true
  10. Enter the field map script provided below for the coalesce field map.
  11. Add the onBefore script provided below to the transform to not create new records.
  12. Save and run the transform.
  13. When the transform completes, click on the import set number.
    The import set is displayed.
  14. Sort the import set rows section by "Row" ASC.


Coalesce field map script:

answer = findMe();

function findMe() {
if (source.u_myid == 'skip me') {
return null;
} else {
return source.u_myid;


onBefore transform script:

if (action == 'insert')
ignore = true;


There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field to determine the versions that have a permanent fix. Subscribe to the known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

Related Problem: PRB627466

Seen In

Eureka Patch 5
Fuji Patch 12 Hot Fix 1
Geneva Patch 4

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-09-16 01:16:14