Application File Imports Release Notes Sync Web Services FAQ

File Importing Errors

There are various warnings and error messages that can be encountered as a result of a file import.  The information within this page covers some common error messages and how to resolve them. 

Almost all files can be re-imported without duplication or mishandling of data after the problems have been resolved.  If you are unsure about the file specification you are working with, please contact ALP SaaS Support.

 

General Errors

Invalid Address Region

The state/province/region for the referenced country is not setup within the database.

Common resolutions for this include:

  • Correct the file data -- the region code and/or country code is invalid.
  • Update region information -- the referenced country has 'fixed regions' when it should not, or the region is not configured for the country.

Unknown Location Translation

The location identifier within the file does not have a corresponding location translation setup within the database.

Common resolutions for this include:

  • Correct the file data -- the vendor should not have included this data, or the data is invalid.
  • Create the location and/or location translation -- either one or both may not exist.

Unknown Member

The account Id referenced in the file is not assigned to a member within the database. 

Common resolutions for this include:

  • Correct the file data -- the account ID cited in the file is incorrect.
  • Enroll the missing member -- Member with the account ID is not currently in the system.
  • Assign the account Id to an existing member -- Member exists, but the account ID is not assigned to their account.

Parimutuel-specific Errors

Unknown Parimutuel Pool

The parimutuel pool referenced in the file is not configured within the system.

Common resolutions for this include:

  • Update the parimutuel pool configuration -- The pool does not exist within the database, or is incorrectly configured.

Unknown Parimutuel Track

The parimutuel track referenced in the file is not configured within the system.

Common resolutions for this include:

  • Update the parimutuel track configuration -- The track does not exist within the database, is incorrectly configured, or the tote changed the code within their system.

 

Aimia Logo

Please note: All external ALP SaaS links and references are directed to US datacenter unless specifically noted.

Tags:
Home: Aimia Loyalty Platform SaaS Copyright © 2020 Aimia Inc. All Rights Reserved.