Data source fields
This article is based on the ServiceNow documentation article. See the original article on the ServiceNow doc site: ServiceNow: Data source fields.
Additional fields appear on the data source form depending on the value of the Type field.
Quality Clouds tip
The Use last run datetime selection controls the amount of data that is retrieved from a database during an import run. If this check box is deselected, then all rows in the table specified are imported, every time. You might want to use this setting if this is a one-time import, or if all the data in the target table is new. If this check box is selected, two additional fields appear, enabling you to select a datetime value to limit imported data to delta values only. QualityClouds raises a warning for each JDBC Data Source which has this check box unselected, as a reminder that it is usually more efficient to selectively import data.
Field type data source fields
These additional fields appear on the data source form when the Type field value is File.
| Field | Description |
|---|---|
| Format | Select one of the following formats from the list: CSV, CSV (tab), Custom (Parse by Script), Excel, JSON, XML. |
| Zipped | Select this check box if the import file is compressed. |
| Xpath for each row | Specify an XPath expression that selects the nodes which become rows in the import table. The children of the selected nodes will become the columns in the rows. |
| Expand node children | Select this check box if child elements of the XML node or JSON object should be converted into additional columns. Clear this check box if the parent column value should be an XML or JSON fragment. For JSON, note that selecting this option expands objects only, not arrays. For nested array support, see Importing JSON files. |
| File retrieval method | Choose the appropriate retrieval method for this file. |
| File path | Specify the path to the file to import.You can include a system property value in this field using the format ${system.property.name}. When the connection is made, the variable is replaced with the value of the specified property. For files retrieved using HTTP or HTTPS, the property glide.ds.file.http.variable_replacement must be true to use system property expansion. For example, you can specify the File path value /countries.csv?key=${datasource.apikey}. When the connection is made, the value of the datasource.apikey system property is passed as the value for the key parameter. For HTTP and HTTPS protocols, the file path is automatically URL encoded. Do not specify a URL-encoded file path when using either of these protocols. |
| SCP authentication method | Select to authenticate with a Username and Password or with a Public key. Note: You cannot authenticate to data sources with a public-private key pair. Use a username and password authentication instead. |
| Server | Enter the name of the server from which the file will be imported.You can include a system property value in this field using the format ${ystem.property.name}. When the connection is made, the variable is replaced with the value of the specified property. For files retrieved using HTTP or HTTPS, the property |
| Port | Enter the port to use to connect to the specified server. This field appears if you select HTTP or HTTPS as the file retrieval method. |
| User name | Enter the user name for authentication on the file server. |
| Password | Enter the password for authentication on the file server. |
| Private keyfile | Specify the keyfile when using legacy SCP public-private keyfiles. You cannot authenticate to data sources with a public-private key pair. Use a username and password authentication instead. |
| System KeyStore | Select this check box to validate the certificate from the FTPS server against all saved certificates. This certificate may be any type supported by the instance. If you do not select this check box, the instance uses the Java default certificate to validate the FTPS server. This field is available only for data sources with a File retrieval method value of FTPS. All FTPS file retrieval methods are supported, including Auth TLS, Auth SSL, Implicit SSL, and Implicit TLS. |
JDBC type data source fields
These additional fields appear on the data source form when the Type field value is JDBC.
| Field | Description |
|---|---|
| Use MID Server | Select a MID Server to use to connect to this data source. |
| Format | Select one of the supported database formats. Instances can connect to Microsoft SQL Server 2012 but not Microsoft SQL Server 2000. |
| Instance name | Used to support dynamic port connectivity with SQL Server. To ensure connectivity, provide the instance name for a SQL Server that receives a new port number dynamically after each reboot. This field only appears when SQLServer is selected as a data source format. |
| Database name | Enter the name of the database instance. |
| Database port | Enter the port number for the database. Leave this field empty when using dynamic port connectivity with SQL Server. |
| Use integrated authentication | Select this check box to allow the JDBC connection to use the ID of the user configured for the Windows MID Server service for SQL Server authentication. For additional details, see JDBC type data source. |
| User name | Enter the user name for authentication on the database server. The user name provided for the JDBC connection must be associated with an account on that database server; it cannot be a Windows Domain account. |
| Password | Enter the password for authentication on the database server. |
| Server | Enter the name of the server from which the data will be imported. |
| Query | Select the type of query to run: All rows from Table or Specific SQL. If you select to run a SQL statement, the SQL statement field appears. |
| Query timeout | Specify the number of seconds the JDBC driver will wait for a query (SELECT) to complete. Zero means no timeout. If timeout is exceeded, the integration considers the JDBC result inaccessible and places it in an error state. |
| Connection timeout | Specify the number of seconds before MID Server connection cache pool closes and removes it from the pool. Zero means no timeout. |
| Table name | Type the name of the table from which the data is being exported. |
| SQL statement | Type a SQL statement to extract the desired data from the database. |
| Use last run datetime | This selection controls the amount of data that is retrieved from a database during an import run. If this check box is unselected, then all rows in the table specified are imported, every time. You might want to use this setting if this is a one-time import, or if all the data in the target table is new. If this check box is selected, two additional fields appear, enabling you to select a datetime value to limit imported data to delta values only. |
| Last run datetime | The datetime value in this field is automatically populated from the database field you select below and represents the latest value from the previous run. This value acts as a dynamic filter to restrict the number of records retrieved to those records that have changed since the data source's last runtime. |
| Last run database field | Select the field name from the source table that will be used as the filter in the next run. This value may need to be case sensitive depending on the target database type. |
| Additional Database Parameters | Optional parameters to add to the end of the URL generated for this data source. Enter a semicolon-separated list of parameters. You may need to configure the form to view this field. |
LDAP type data source fields
These additional fields appear on the data source form when the Type field value is LDAP.
| Field | Description |
|---|---|
| LDAP target | Select a target from the list of your LDAP OU definitions. |
