Data upload error handling
During the file upload, if the files are not created or filled out properly, you may encounter specific error, fatal error, or warning massages. Depending on the error type, the application will handle the files differently:
In case of a warning, the files are still processed.
In case of an error or fatal error, the .csv files containing the error are not processed. They then must be corrected and uploaded again.
This article details the various errors that you might encounter at data upload and their cause.
Data foundation validations
The following table lists the errors related to the data foundation validation mechanisms that you may encounter.
| Message | Message Type | Cause |
|---|---|---|
| Failed to find {fileName}.csv | A csv file is missing. | |
| Failed to parse {fileName}.csv. Missing headers: {missingFieldName} | A column is missing in a .csv file. |
|
| Error. in {entityName} with externalId: null. Field: externalId. Description: Required data is missing or has invalid value. | Error | An externalId value is not provided. |
| Error. in {entityName} with externalId: {externalId}. Field: effectiveDate. Description: Required data is missing or has invalid value. | Error | ExternalId exists but the effective date is not provided. |
| Error. in {entityName} with externalId: {externalId}. Field: effectiveRangeEndDate. Description: Required data is missing or has invalid value. | Error | ExternalId exists but the effective range is not provided (start or/and end date) |
| Error. in {entityName} with externalId: {externalId}. Description: Error in effective dates | Error | Effective range is provided, but a range conflict exists in one externalId. |
| Error. in {entityName} with externalId: {externalId}. Description: Error in effective dates | Error | Unique identifier (ExternalId+effective date) is duplicated. |
| (high prio bug) AC-8044: No error when primitive field has type error | A type error was found in a primitive field. | |
| Error. in {entityName} with externalId: {externalId}. Field: {missingValueField}. Description: Required data is missing or has invalid value. | Error | A primitive or relationship field is required and its value is NULL. |
| Error. in {entityName} with externalId: {externalId}. Field: {incorrectEnumField}. Description: Data does not meet the specified constraints. Enum value {incorrectEnumValue}. is not in the possible values. | Error | An enum field is required and the referenced value does not exists. |
| Error. in {entityName} with externalId: {externalId}. Field: {incorrectEnumField}. Description: Errors found in optional fields. Enum value {incorrectEnumValue}. is not in the possible values. | Error | An enum field is optional and the referenced value does not exists. |
| FatalError. Description: Relationship value: {notExistingIdentifier} not found in {referencedEntityName}. Entity is missing or has invalid state | Fatal Error | A relation field is required and the related entity distinct identifier does not exist. |
| Warning. in {entityName} with externalId: {externalId}. Field: {incorrectReferenceField}. Description: Errors found in optional fields. ExternalId does not exist. | Warning | A relation field is optional and the related entity distinct identifier does not exist. |
| Failed to parse {fileName}.csv. Unrecognized headers: {incorrectFieldName} | Additional columns detected in the .csv file. |
IAM validations
The following table lists the errors related to the IAM service validation mechanisms that you may encounter.
| Message | Message Type | Cause |
|---|---|---|
| FatalError. in OrgStructure Field: parentOrgStructure. Description: Cyclic dependency detected between OrganisationItems.: {OrganizationItem1} -> {OrganizationItem2} -> {OrganizationItem1} | Fatal Error | Circular dependency between organization items. |
| FatalError. in Worker Description: Couldn't create users: Unable to save changes because a circular dependency was detected in the data to be saved: 'User [Added] ReportsTo Subordinates { 'ReportsToId' } <-\nUser [Added] ReportsTo Subordinates { 'ReportsToId' } <-\nUser [Added]To show additional information call 'DbContextOptionsBuilder.EnableSensitiveDataLogging'.'. | Fatal Error | Circular dependency between line manager id. This error can only occur when adding new workers. No error occurs when updating workers. |
| FatalError. in OrgStructure Description: Couldn't update org-items. Multiple root org-items found. ExternalIds: {externalId1}, {externalId2} | Fatal Error | There are multiple roots in the organization item. |
| FatalError. in OrgStructure Description: Couldn't create org-items. Multiple root org-items found. ExternalIds: {externalId} | Fatal Error | Organization items are already committed and the root organization external id is changed. |
| root manually disabled from iam.OrganisationItems then sending new file with active = true | The root organization in IAM is disabled iam.OrganisationItems. | |
| Synchronizing root organization active = false | ||
| no error. cannot replicate / user should not exists in hr-data → to replicate | AnemployeeId is null in iam."MyIdentityUsers". | |
| When updating existing data → changing user name Error and FatalError FatalError. in Worker Field: UserName. Description: Couldn't update users: An error occurred while saving the entity changes. See the inner exception for details. UserName field should be unique. | Fatal Error | There are two identical usernames for different externalIds in the Worker entity when updating records. |
| FatalError. in Worker Description: Couldn't create identity users: 23505: duplicate key value violates unique constraint \"UserNameIndex\"\n\nDETAIL: Detail redacted as it may contain sensitive data. Specify 'Include Error Detail' in the connection string to include this information. | Fatal Error | There are two identical usernames for different externalIds in the Worker entity when inserting records. |
| When updating existing data → changing worker email Error and FatalError FatalError. in Worker Field: Email. Description: Couldn't update users: An error occurred while saving the entity changes. See the inner exception for details. Email field should be unique. | Fatal Error | There are two identical worker email addresses for different externalIds in the Worker entity when updating records. |
| When inserting data FatalError. in Worker Field: Email. Description: Couldn't create users: An error occurred while saving the entity changes. See the inner exception for details. Email field should be unique. | Fatal Error | There are two identical worker email addresses for different externalIds in the Workerentity when inserting records. |
Going further