Exploring the Data Import Process

Objective

After completing this lesson, you will be able to import records into the system manually.

Validation During the Import Process

The import process includes two default validation checks.

Data Type: Prohibits importing alpha characters into a numeric field.
Data Length: Prohibits importing a field longer that specified in the database schema.

Additional validations can be manually added in the Entity Edit functionality or in the Import Format field mapping definition.

In the example in the Import Request section, the Import request ended in Error. Select the View Messages or View Log icons to reveal descriptions of the error.

An import request that has returned an error. The Information icon is highlighted.

In this case, the CustomerId value was 48 characters, but the InCustomer.CustomerId field has a limit of 30 characters.

he message log detail of an import request, showing that the character limit has been exceeded.

Hint

Avoid relying on errors in Import Requests to ensure data integrity, as errors cannot be resolved in the user interface. The record(s) in error will need to be identified/resolved and reimported in another Import Request. The best practice is to add validations as part of the post process so the errors can be corrected in the user interface if possible.

Import a List of Customers Manually

Business Example:

In this exercise, you will manually import a list of customers using the TrainCustomerImport.xlsx.

ExerciseStart Exercise

Steps

Create an InFile record and add basic data.
1. From the Integration Portal, select Inbound Data→File Search.
2. Select New (+).
3. Populate the fields with the following:
  - File ID: CustomerImport
  - Name: Customer Import
  - Eff Date: 1/1/2025
  - Process Month: 2
  - Process Year: 2025
  - Payout Type ID: CLIENT Payout
  - Comments: Customer Import for Training
4. Select Save.
Add an import file.
1. In the Import Requests section, select +.
2. On the Import Format dropdown, select TrainingCustomer.
3. Set the Upload Type to Client.
4. In the File Content field, select Choose File.
5. Navigate to TrainCustomerImport.xlsx and select Open.
6. Select Next.
  The Import Request Summary screen of the wizard appears with the ID of the new Import Request.
7. Select Complete.
  The data is uploaded into the appropriate staging tables based on the Import Format. The File Detail screen is updated as shown below.
Manually Resolve Import Errors
It looks like our import had an error! In this step, we will find and resolve the error.
1. Select View Messages to reveal descriptions of the error.
2. Hover over the Error row to display the full description of the error. In this file, line 13 is invalid because the CustomerId is too long.
  Note
  There is no way to correct this error in the user interface since the data hasn’t been committed to the database. To correct this issue, we’ll correct the data in the source file and reimport.
3. Open the TrainCustomerImport.xlsx file.
4. Delete the first 12 rows of data.
5. Move row 13 up to row 2, just below the header.
6. Change the Customer ID in the row to Training12 and save the file.
Repeat the import process
1. In the Import Requests section, select +.
2. From the Import Format dropdown, select TrainingCustomer.
3. Set the Upload Type to Client.
4. Select Choose File and select the fixed file.
5. Select Open.
6. Select Next.
7. Select Complete.
  Note
  The Import Requests list should look like the following image.

Summary

The import process has two default validation checks: data type and data length.
Additional validations can be configured in Entity Edit.
A best practice is to add validations as part of the Post process so errors can be corrected in the user interface.

Next lesson