This solution is for customers with a GAIS Premium subscription.
When using the GAIS API-endpoints you might run into error codes and experience missing updates of the Organisation on the GAIS-platform due to these. There error codes are intentional and implemented in areas where differences between the existing data on the platform and the new data from integration might result in unintended data loss or inability to use certain functions.
If the differences are intentional you can always overwrite the error by manually uploading the same file in the User Interface where you'll be asked to confirm any changes and mapping.
Error codes will be available on the 'Update history'-page in the User Interface along with any attempted data upload to the organisation.
Any rejected or errored file will display one or more of the following error codes:
Error code | Message | Description | Integration consequence |
5012 | IMPORTED_NUMBER_OF_MEMBERS_DIFFER_MORE | Imported number of members differs by more than 10% | Import aborted |
5002 | Error.SUPERIOR_EMAIL_MISSING | Some superiors doesn't have an entry and could not be mapped - entries compared on email | Import aborted |
5000 | Error.EXISTING_UNITS_MISSING | If unit mapping is enabled, all the units from the current org configuration must be present in the imported columns | Import aborted |
5001 | Error.SUPERIOR_REF_COLUMN_MISSING | If superior mapping is enabled the uploaded file must contain the same superior ref column | Import aborted |
5001 | Error.SUPERIOR_REF_COLUMN_MISSING | If the superior mapping is enabled and the file contains the superior ref column, all superiors referenced must still have valid emails in the uploaded file | Import aborted |
5003 | Error.EXISTING_ATTRIBUTE_COLUMN_MISSING | If any attribute is currently mapped, the uploaded file must still contain the mapped attribute | Import aborted |
5004 | Error.EXISTING_LANGUAGE_REF_COLUMN_MISSING | If language mapping is enabled, the uploaded file must contain the mapped column used for defining languages (LanguageRefColumn) | Import aborted |
5005 | Error.SUPERIOR_NAME_MISSING | If superior mapping is enabled, but the reference is the name column instead of an email, all referenced superiors must have a valid value in their corresponding name field | Import aborted |
5006 | Error.UNMAPPED_LANGUAGES_FOUND | If language mapping is enabled and the file contains the correct language reference column, all referenced languages must be mapped to a valid value | Import aborted |
5009 | Error.DISTRIBUTION_COLUMN_MISSING | If distribution is mapped to a column (distributionRefColumn), this column must be present in the uploaded file | Import aborted |
50010 | Error.DISTRIBUTION_COLUMN_MISSING | If distribution is mapped, mobileRefColumn is defined then a valid mobile column must be defined | Import aborted |
5011 | Error.IMPORTED_COLUMNS_DIFFER | The amount of columns, not counting email and name, should not differ in the uploaded file | Import aborted |
5013 | Error.IMPORTED_DUPLICATE_EMAILS_FOUND | The email column cell values should only contain unique emails in the uploaded file | Import aborted |
5014 | Throw IMPORTED_INVALID_EMAIL_ADDRESS | All emails must be valid emails in the imported file | Import aborted |
5015 | Throw IMPORTED_EMPTY_MEMBER_NAME | All names in the imported file must be valid (not null or empty) | Import aborted |
5007 | Error.MOBILE_COLUMN_CONFIG_MISSING | If distribution has been mapped (distributionRefColumn), and one or more values contain "sms", and there is an associated (mobileRefColumn), this column must be present in the uploaded file. | Import aborted |
5008 | Error.BAD_MOBILE_NUMBER_VALUE | If distribution is mapped and mobileRefColumn exists in the uploaded file, then the value in the referenced phone number cell must be a valid phone number | Import aborted |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article