...
The import batch process is initiated by uploading an import file, which contains the data that will be used to create manual items in interpreted timesheets that have not been reviewed. The import file must be formatted so the system can read the file and its content. For example, the first row of the import file must contain column headers that can be mapped to FastTrack interpreted timesheet manual item. For more information, see Import File Format Validation.
Defining the Field Mapping
...
A set of field mappings that are configured when importing an import file can be saved as a template, which can be applied whenever an import file that originates from the same source is processed in the future. This prevents the need to manually configure the field mapping each time an import is processed. For more information, see Saving Field Mapping Templates.
Queuing the Import Batch for Processing
Once the field mapping has been configured it is possible to queue the interpreter manual import batch for processing. On attempting to queue an import batch for processing, the system performs field mapping and data type validation to ensure that manual items can be theoretically created based on the mapping and types of data provided within the import file. For more information, see Field Mapping & Data Type Validation.
If the validation succeeds the import batch is sent to the Process Queue, where the batch undergoes processing. The amount of time that it takes for a queued batch to complete processing depends on a number of factors such as the following:
the number of prior import batches already queued for processing the number of individual rows within the import file.
...
If a system error occurs when an import batch is queued for processing the status of the batch will be set to Failed and no manual items will be created in interpreted timesheets in Interpreter Review. If this occurs, you will need to process the original import file as part of a new manual item import batch.
| Info |
|---|
Where the same information is imported via two different import batches, the manual item will display as two different items in the Interpreter Review > Interpreter Timesheet Details screen. However, if you edit any of the items within the Interpreted Timesheet, the system will consolidate any transactions where the same item/date/values etc exist, so the two imported items will be combined. This is standard behaviour even where a user enters the same information twice via the UI. In the Audit Tab however, the two separate transitions will display. Where the manual item is imported via an API call, if the same scenario exists (same item/date/values), the API import will call the UI logic and automatically combine the two separate call items. |
| Child pages (Children Display) |
|---|
...