{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22242,"path":"integrate-applications/system-import-sets/t_CreatingAFieldMap.md","title":"Create a field map","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a field map\n\nField maps establish a relationship between a field in an import set table and a field in the target table.\n\n## Before you begin\n\nRole required: import\\_transformer, import\\_admin, or admin\n\n## About this task\n\nThe field map determines what values from the source table the transformation adds to the target table.\n\n## Procedure\n\n1. Navigate to **All** > **System Import Sets** > **Transform Maps**.\n\n2. Open a transform map.\n\n3. In the **Field Maps** related list, click **New**.\n\n4. Complete the form.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nMap\n\n\n\nTransform map that uses this field mapping \\(populated automatically\\).\n\n
\n\nSource table\n\n\n\nTable from which the raw import set data is loaded \\(the source for the transformation\\). Populated automatically from the transform map.\n\n
\n\nSource field\n\n\n\nField on the source table to be transformed. Can be blank if the **Source table** contains only raw data.\n\n
\n\nChoice action\n\n\n\nSpecifies the action to take if the import set contains a reference or choice value other than those available. Appears if the target field is a choice list or reference field.- **create**: Create a new choice or record in the reference table.\n- **ignore**: Ignore the new value from the source table.\n- **reject**: Skip the entire row \\(record\\) containing the new value and continue to the next row.\n\n\n
\n\nDate format\n\n\n\nDate format of the source field. Appears if the target field is a Date or Date/Time field.**Note:** To learn more about allowable date formats, see [Global date and time field format](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_FormatDateAndTimeFields.md).\n\n
\n\nUse source script\n\n\n\nCheck box to use a script instead of the **Source field**.\n\n
\n\nApplication\n\n\n\nApplication scope: global or per application.\n\n
\n\nTarget table\n\n\n\nTable in which the transformed data is inserted. You can select only tables within the currently selected application scope or the global scope, or tables that grant write access to other applications.\n\n
\n\nTarget field\n\n\n\nField in the target table where the value from the source field is stored.\n\n
\n\nReferenced field value name\n\n\n\nWhen the target field is a reference field, the transform map needs a way to match incoming source values to existing records in the reference field's source table. Since most imports do not provide a 32-character sys\\_id value, you must specify a column from the reference field's source table that contains values that match the incoming source values.When there is a matching record, the transform map stores the sys\\_id of the matching record in the target field. If there is no matching record, the transform map creates a new record in the reference field's table and stores the sys\\_id of the new record in the target field.\n\n If you leave this field blank, the transform map looks for matching values from the display value column of the reference field table.\n\n For example, suppose you are importing incident records and the incoming data lists user IDs for the **Assigned to** field. If you leave **Referenced value field name** blank, the transform map searches for matching values in the User table's display value column: name. By setting the **Referenced value field name** to the user\\_name column, you can match the user ID values to the appropriate user records.\n\n
\n\nCoalesce\n\n\n\nConfiguring a target field to coalesce causes the import set to treat the field as a unique key. When selected, the import set application attempts to match source values to records with values from an existing record. If a match is found, the transform map updates the record instead of creating a new record. When false, the import set application always creates new records for each transformation. If multiple fields are set to coalesce, all coalesce values must match an existing record. If two fields are set for coalescing and a matching value is found for one of the coalescing fields but not on the other, a new record is inserted.You must create an index on the target table if none of the coalesce fields are indexed. Indexing can improve performance for read and write operations. If one or more coalesce fields already has an index, you do not need to create an additional index.\n\n After setting the **Coalesce** value for all fields on the target table, use the **Index Coalesce Fields** related link to create an index. Before creating the index, ensure that the **Coalesce** value is set correctly for all fields on the target table to avoid creating unnecessary indexes for the same target table.\n\n The index needs to be concatenated; meaning all fields specified to be coalesced, need to be in the same index. The correct setup is for one index to include all fields being coalesced.\n\n
\n\nCoalesce empty fields\n\n\n\nCheck box to match an empty source field value to an empty target field value. For example, the User transform map coalesces on the email field. With this option selected, a source record containing an empty email address coalesces to a target record containing an empty email address.\n\n
\n\nCoalesce case sensitive\n\n\n\nCheck box to make case-sensitive coalesce values result in the creation of new records. By default, values marked as **Coalesce** are used in a case-insensitive lookup for existing records. Case-insensitive records update existing records only and do not cause the creation of new records.\n\n
5. Click **Save**.\n\n6. Repeat steps 3-5 for each field mapping.\n\n7. Click **Update**.\n\n\n**Parent Topic:**[Importing data using import sets](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/system-import-sets/c_ImportDataUsingImportSets.md)\n\n"}}