Minimum Version Required: 22.01
Pre-Conditions
User must have TableImport permission to execute this routine
The ImportRoutine values must correspond to existing import routines in the system
If updating existing records, valid ImportTaskIDs must be provided
Steps
The ImportTasks EDBL routine allows importing or updating records in the ImportTasks table. This table tracks import operations that have been performed in the system. The routine handles mapping external import routine names to internal IDs and manages status values.
When the routine runs:
It translates ImportRoutine names to ImportRoutineID values using table translations
It validates ImportRoutineIDs against existing records in the system
It processes Status and StatusID fields to ensure consistency
It calculates StartDate and EndDate values based on CloseDate or fallback values
It adds or updates records based on your selected import action
Null ImportRoutineID values will occur if the system cannot find a matching import routine. These records will fail validation during import.
Fields And Definitions
ImportTaskID - Integer, primary key of the ImportTasks record. Required for update operations.
ImportRoutine - Text, the name of the import routine to run. This will be translated to an ImportRoutineID using table translations.
CloseDate - Date, when the import task was completed or closed. Used to calculate EndDate.
Status - Text, the status of the import task. Values like "New" will be translated to appropriate StatusID values.
StatusID - Integer, numeric representation of Status. When Status="New", StatusID=0; otherwise StatusID=1.
Generated Fields:
StartDate - Calculated as (EndDate + 1 day) or the ImportRoutine creation time
EndDate - Set to CloseDate or defaults to 2001-01-01 if not provided
Best Practices
Always provide ImportRoutine values that match existing import routines in the system
When updating existing tasks, always include the ImportTaskID field
For new tasks, set Status to "New" (StatusID=0)
For completed tasks, provide a valid CloseDate
Ensure external ImportRoutine values have proper translations if they differ from internal names
Review any warnings returned by the import process as they may indicate records that were not properly processed
Before large imports, test with a small sample to verify field mappings are correct