AX1396

Import Wizard: General tab

On the General tab of the Import Wizard, you can define general properties for the import—such as the import name and save options.

Item Description

Import Name

The name of the import. The import name is how you access and execute imports from the Imports menu, and in other areas such as the Import ETL Package task in Scheduler.

Description

Optional. The import description. The description can be used to document the purpose of the import and/or to detail important import instructions. The description is limited to 2000 characters.

When an import is opened in execute-only mode, the description can be viewed by clicking the Show description link in the Execute Import dialog.

Save Options

The save options impact how data is saved to the destination table when the import is executed.

Item Description

Ignore lookup and key errors

Specifies the import behavior if lookup and key errors exist in the temp table data before saving to the destination table. These errors include invalid lookup data, blank keys, and duplicate keys.

  • If enabled, then any rows with lookup and key errors are ignored, and only valid rows are saved to the destination table. Once the import is complete, an error log is provided to detail the invalid rows. For more information, see Import validation errors.

    This option allows you to continue to save valid data even if invalid data is present. You can then investigate the invalid data, make corrections, and reimport.

  • If disabled (the default setting), then the import is aborted if any lookup and key errors exist in the temp table data. No data is saved to the destination table.

NOTES:  

  • If this option is enabled and the import is executed by Scheduler, the execution status of the job is set to Partial Success if any errors are found. This will result in an email notification if the job is set to notify only on error.

  • This option does not apply if a Pre-Save Validation function is used in the import's transform steps. If this function is used, then the import is aborted if any validation errors are found, and no further import steps are processed.

  • Duplicate keys count as an error condition when saving to a reference table, or when Aggregate rows on final save is disabled.

Aggregate rows on final save

Specifies whether duplicate rows are aggregated during the final save to the destination table. Duplicate rows are rows that have the same key column values.

  • If enabled (the default setting), then duplicate rows are aggregated before saving data to the destination table. This aggregation process may take some time for large imports.

  • If disabled, then the temp table data is not aggregated before saving data to the destination table. If any duplicate rows exist, the import is aborted and no data is saved to the destination table. You can optionally use the Ignore lookup and key errors option to instead exclude the invalid rows and only import valid rows.

Disabling this option may improve import performance for large imports where aggregation is not necessary.

NOTE: This option does not apply when the destination table for the import is a reference table, or any table with an identity key column.

Bypass updating existing rows when saving to the destination table

Specifies whether the import saves both updated data and new data, or just new data.

  • If enabled, then only new records of data are saved to the destination table when the import is run. Updates to existing records are ignored.

  • If disabled (the default setting), then new records and updates to existing records are saved to the destination table when the import is run.

Enabling this option may improve import performance for use cases where the import source is not expected to contain updates to existing data. Keep in mind that if you enable the option and the import source does contain updates to existing data, the updates are simply ignored with no warning.

NOTE: If this option is enabled, existing records in the source data may still cause import errors, even though these records will be ignored for the final save to the destination table.