The mapping assist utility provides a visually intuitive environment for specifying mapping between import set fields and production table fields. The mapping assist utility makes it possible to map a single source field (field on an import set table) to multiple destination fields (fields on a production table).

If the date format of the source field does not match the format of the target field, you can set a date format mapping to transform dates from one format to another. For example, this mapping specifies that the date format of the CSV source file uses the MM-dd-yyyy format.

Date format options include:

Table 1. Mapping Options

Date Format	Description
dd-MM-yyyy	Day-month-year
dd-MM-yyyy hh:mm:ss	Day-month-year hours-minutes-seconds
dd-MM-yyyy hh:mm:ss z	Day-month-year hours-minutes-seconds timezone
MM-dd-yyyy	Month-day-year
MM-dd-yyyy hh:mm:ss	Month-day-year hours-minutes-seconds
MM-dd-yyyy hh:mm:ss z	Month-day-year hours-minutes-seconds timezone
yyyy-dd-MM	Year-day-month
yyyy-MM-dd	Year-month-day
yyyy-MM-dd hh:mm:ss	Year-month-day hours-minutes-seconds

ServiceNow duration fields use a special data type that lists the number of milliseconds the duration value is. To map import data to a duration field use one of the following methods to transform source values into a duration.

• Calculate the duration from a start and end date
• Convert an existing duration value into a ServiceNow duration value

If the import source has a start and end date, you can calculate a duration with JavaScript.

1. Navigate to System Import Sets > Transform Maps.
2. Select the transform map you want to calculate a duration value. For example, the Notification transform map that imports into the Incident table.
3. Select the Run script check box.
4. Enter JavaScript to transform the start and end dates into a duration. See the sample script.
5. Click Update.

This sample script transforms the source.u_start and source.u_end fields to a duration value in the target.duration field. Change the field names to match your source and target fields as needed.

target.duration = gs.dateDiff(source.u_start.getDisplayValue(), source.u_end.getDisplayValue(), false);

If the import source already contains a start date and a duration value, you can convert the existing duration into a ServiceNow duration. For example, you might have an Excel data source that lists a duration in seconds. ServiceNow expects durations to have millisecond values.

1. Navigate to System Import Sets > Transform Maps.
2. Select a transform map.

   For example, the Notification transform map that imports into the Incident table.

3. Select the Run script check box.
4. Enter JavaScript to convert existing duration values into a ServiceNow duration values. See the sample script.
5. Click Update.

This sample script converts a duration in seconds (from the source.u_duration field) to a duration in milliseconds (in the target.duration field). Change the field names to match your source and target fields, as needed.

//Transform the value in source.u_duration from seconds to milliseconds
target.duration.setDateNumericValue(source.u_duration * 1000);

This sample script converts a duration already in milliseconds (from the source.u_duration field) to a ServiceNow duration (in the target.duration field). Change the field names to match your source and target fields, as needed.

//Transform the value in source.u_duration to ServiceNow format
target.duration.setDateNumericValue(source.u_duration);

You may want to use a source script instead of the Source field when:

• The source value is not in the format for the mapped target value.
• You want to look up a value before mapping to the target field.
• The source value must be computed from multiple fields.
• You need to create a compounded or calculated coalesce value in the target field.

For example, this example source script computes the value of the user_name field when it is blank in the source.

To have a transform map access the attachment, use the GlideRecord API in an onAfter script. The script needs to run in an onAfter event because the target.sys_id object is only available after the data is placed in the import set table. For example, to map the resulting attachment to the target transform record, you can use the following script.

var agr = new GlideRecord("sys_attachment");
  agr.addQuery("sys_id", source.u_blob_field);
  // the source field needs to be mapped to the source that is the BLOB
  agr.query();
   if(agr.next()) {
    agr.table_name = "cmdb_ci"; // the target table of the transform map
    agr.table_sys_id = target.sys_id; // the target record
    agr.content_type = source.u_contentype; 
    // the content type string if available,  
    // this becomes the mime encoding when clicking an attachment link
    agr.update(); // finally, move/re-attach the attachment to the target row }

If you are mapping directly to the db_image table, run the following onAfter script to display the image:

var strTemp = source.u_file_name; 
var fType = strTemp.substr(- 3); 
var iCont = "" ;
 
 if(fType == 'jpg') {
  iCont = 'jpeg' ; } 
 else {
  iCont = fType; }
 
 var agr = new GlideRecord("sys_attachment");
 agr.addQuery("sys_id", source.u_blob_field);
 agr.query();
 
 if(agr.next()) {
  agr.table_name = "ZZ_YYdb_image";
  agr.table_sys_id = target.sys_id;
  agr.content_type = 'image/' + iCont;
  agr.file_name = 'image';
  agr.update(); }