System Import Sets

Create a data source record to define what data an import set should import.

Create a web service import set table to define how to stage and transform imported data.

A transform map is a set of field maps that determine the relationships between fields in an import set and fields in an existing ServiceNow table, such as Incident [incident] or User [sys_user].

Data sources are used to create an import set so that data can be processed, if necessary, prior to being mapped onto a production table.

To import data define a data source and transform map, and run or schedule an import.

There are several methods for moving data from one instance to another.

The coalesce option allows you to update existing target table records when transforming import data.

Learn about import sets before importing data to your instance.

Explicitly define mapping relationships in the Transform Map record itself.

You can map fields in a number of ways depending on the circumstances of the import and whether data must be transformed prior to loading onto a production table.

Web Service Import Sets use the same security mechanisms as SOAP Web Services.

Review these performance issues to troubleshoot and improve the performance of your import set jobs.

The import log is where you can find information about the internal processing that occurs during an import operation.

Web service import sets complement direct web services and scripted SOAP web services providing a web service interface to import set tables.

Use an XML import set to import data from another instance.

You can directly export records as XML from any list or form.

Split incoming data into multiple import sets and transform the import sets concurrently to reduce processing time.

Create a Custom (Load by Script) type data source record to define what data an import set should import.

Create a Data Stream (IntegrationHub) type data source record to define what complex data an import set should import from a Data Stream action.

Create ETL definitions to extract data from a source table, transform the data as desired, and load the data into multiple target tables. ETL definitions also support nested data structures.

Define the entity fields mapped for Extract Transform Load (ETL) operations.

Create a File type data source record to define what data an import set should import.

Create a JDBC type data source record to define what data an import set should import.

Create an LDAP type data source record to define what data an import set should import.

Create an OIDC type data source record to define what data an import set should import.

Create a REST (IntegrationHub) type data source record to define what data an import set should import from a REST API.

Define how information is sent from the source table to target tables via a Robust Transform Engine (RTE).

Specify your own Robust Transform Engine (RTE) to transfer data from a source table to a target table.

Use a custom script to store any type of incoming data in the import set table.

Enable platform Data Sources to load data from Integration Hub Data Stream actions.

Create and configure a Data Source request action in Integration Hub. After the request action is published in Integration Hub, you can choose it as a Request action in the Data Source record.

Define the Extract Transform Load (ETL) entities used by the Robust Transform Engine.

Map the source entity to a target entity.

Define the operations the Robust Transform Engine (RTE) should perform.

Delete import set tables, related transform maps, or data only (preserving the table structure) to clean up your database.

Delete import sets to clean up your database on a scheduled basis, one time only, or on demand.

ETL definitions extract data from a source table, transform the data as desired, and load the data into one or more target tables. ETL definitions also support nested data structures.

Learn how to set up and use an ETL definition to import data into ServiceNow tables.

View detailed information about import set runs, individual rows in the import set, and import logs.

Import sets enable administrators to import data from various data sources, and then map that data into ServiceNow tables.

Considerations when importing data containing date/time values.

These examples demonstrate how to import various types of JSON data and the necessary path for each row. JSON files that you import should follow these guidelines.

Check the status of concurrent import set jobs.

Monitor concurrent import sets to check the status of import sets and import set jobs, resume or reprocess import sets, and view transform history.

Monitor scheduled data import executions to see the hierarchy and flow of the scheduled chained imports.

Multiple JavaScript objects are available in the Scheduled Data Import Pre script and Post script fields.

In addition to common fields, other fields appear on the data source form, depending on the value of the Type field.

Several predefined variables are available in the Source script field.

Import a file from a local source, a remote network server, or another instance by providing a path and authentication information.

Certain properties are available for customizing your FTP data source.

The import history gives status information about individual import operations.

When a SOAP message inserts a record into an import set table, and there is no import set for that table in the Loading state, a new import set will be created with the Mode set to Synchronous.

Multiple properties control import set behavior.

You can insert multiple records in one SOAP request by using the insertMultiple operation.

A JDBC data source retrieves its data via a JDBC driver, usually type 4 network.

An LDAP data source is automatically created when you configure your instance to integrate with LDAP.

Transformation events occur during the process of transforming an import set table onto a table.

Rows imported using import sets must not exceed the maximum row size.

An example using Perl to post a CSV file with basic auth credentials and Java Apache HttpClient class to post a CSV file with basic auth credentials.

Several Import Set tables are available by default.

Multiple variables can be used to define explicit mapping relationships in a transform map script.

Use robust import set transformers instead of transform maps if you want to extract, transform, and load data to one or more target tables.

Properties that define the types of updates that are permitted.

Create one onBefore transform map script to copy the sys_id of new records from the source to the target instance. Create a second onBefore transform map script to identify records on the target instance that have the same unique values but different sys_id values.

Data sources are used to create an import set so that data can be processed, if necessary, prior to being mapped onto a production table.

Every import operation to a production table requires at least one transform map associated with an import set.

Field maps establish a relationship between a field in an import set table and a field in the target table.

An administrator can post CSV or Excel files directly to instance.

You can process CSV files that are delimited by a character other than commas.

In this method, you import data from another instance using an HTTPS data source to return a CSV formatted file containing the rows to be imported.

After an import set completes, you can review the completed import and clean up import set tables. Even if no errors are reported by the progress indicator, review how your data is imported into the new import set.

You can manually run an import to immediately import data.

Schedule imports to make it possible to specify that certain import operations occur at a regular interval.

Use temporary ETL entities to avoid repetitive operations in target entities.