Troubleshooting Data Feeds

Archer validates the data feeds and reports any errors. If errors are found, Archer ends the data feed process. You must correct the errors in your data file before attempting the data feed again.

Note: By default, the data feed process ends when it encounters an error. However, if you want to continue processing the data feed even if errors exist, select the Data Validation option on the General tab of the data feed configuration before starting the feed.

The following table describes potential errors and resolutions.

Error

Description

Resolution

All simple keys must be mapped for insert.

If your data feed contains new sub-form records, you must map the fields that you selected to serve as the application simple key to the corresponding fields in the field mapping grid.

Verify that the simple keys are correctly mapped.

All simple keys must be mapped for update.

If you are updating existing parent or sub-form records, you must map the field that you selected to serve as the application's simple key to the corresponding field in the field mapping grid.

Verify that the simple key is accurately mapped.

Column mismatch

Your external data file contains a value that does not match the data type of the field to which the value is mapped.

Change the value in your data file to match the data type required by the field to which you are mapping the value.

Could not locate group name

Occurs if your external data file contains a group value that is not a group value established in the system.

Do 1 of the following:

  • Change the group value in your data file so that it matches a group in the system
  • Add the group from your data file to the system from the Manage Groups page in the Access Control feature.

Date does not match expected format

Your external data file contains a date that does not match the date format that you have specified for the import.

Reformat the date value so that it matches the format that you selected in the Data Import Wizard.

Field is required

Your external data file is missing 1 or more values for a required field.

Enter the required values in your import file or change the field in your application so it is no longer a required field.

Field requires a selected value

Your external data file is missing a value for a Values List field that requires a selected value.

Enter the required value in your data file or change the field in your application so that it no longer requires a certain number of value selections.

Imported sub-form record cannot have multiple parents

Occurs if you are importing sub-form data, and the field from the parent record that you selected as the simple key contains non-unique data

Select a unique field value from the parent record to serve as the application simple key.

Invalid IP Address

Your external data file contains a value for an IP Address field that is not correctly formatted.

Reformat the value.

Invalid key(s) for cross application status field for application

Occurs if you are updating records with a Cross-Application Status Tracking (CAST) field and do not specify valid, simple keys for the parent-application and child-application records associated with the CAST field.

Ensure that the simple keys are valid and unique.

Invalid matrix format

Your external data file contains a value for a Matrix field that is not formatted correctly.

Reformat the value correctly.

Invalid number

Occurs if you are importing a value into a Numeric field that contains alphabetic characters

Change the value in your external data file so it contains only numeric characters.

Invalid tracking ID

Occurs if you are doing an import update, and the Tracking ID field in your external data file contains a value that is not a valid tracking ID for the application into which you are importing

The tracking ID value may not exist in the system, or it may be a valid tracking ID for another application.

Change the value in your data file so that it is a valid, unique tracking ID for the import application.

Multiple columns are mapped to the same field

Occurs if more than 1 field from your data import file is mapped to the same application field

If you are performing a sub-form data import, a field from your data import file may be mapped to the same field as the parent record.

Ensure that your application fields are mapped to different fields and that the import data fields are mapped to the sub-form fields.

Number is larger than maximum value

Occurs if you are importing a value into a Numeric field that is above the maximum value allowed for the field

Examine the Numeric field in your application to determine the maximum value it allows and change the value in your data file to fall at or below that maximum value.

Number is smaller than minimum value

Occurs if you are importing a value into a Numeric field that is below the minimum value allowed for the field

Examine the Numeric field in your application to determine the minimum value it allows and change the value in your data file to fall at or above that minimum value.

Too many cross references

This error can occur:

  • If a record in your external data file contains more values for a Cross-Reference field than the maximum number of value selections than that field allows.
  • If the key field for the cross-referenced application is not unique and your Cross-Reference field maps to 1 of the non-unique values.
  • Examine the Cross-Reference field in your application to determine how many values can be selected for the field, and reduce the number of values in your data file so that they fit within that limit.
  • Verify that the key field of the cross-referenced application is unique.

Unsupported import type

Occurs if you are importing new records and attempt to import data into a Tracking ID field

On the Field Map tab, remove the mapping from the Tracking ID field.

Unsupported link type

Occurs if you are updating records with your data import and you select a field type for the key field that cannot serve as the key field for a record

Examples of field types that cannot serve as the key field for a record include:

  • First Published Date
  • Last Updated Date
  • Record Status
  • Related Records

Select a field type for the key field that can serve as the key field for a record.

The job process (####) ended abruptly for unknown reasons in HH:MM:SS.

Possible causes include a job that was ended by the system administrator or by the job engine (due to being unresponsive). Check the job log files for possible information about any errors.

This error produces a log similar to the following:

<JobType>ArcherTech.DataFeed.Workflows.
WF4.MultistepProcessing.DataFeedScriptExecutionJob, ArcherTech.DataFeed, Version=Maj.Min.NNNNN.BBBB, Culture=neutral, PublicKeyToken=null</JobType>

This error can be caused by the job exceeding the allocated memory limit provided.

In the JavaScript Transporter Settings section of the Archer Control Panel, allocate additional memory in the Max Memory Limit field.

Data feeds configured to run by reference do not run.

Data feeds configured to run after a reference feed runs successfully, fail to run.

Review the Run Details report for the reference feed and the Archer log files to resolve reported failures.