In case an import is complete with 100% import success but the data in Indeavor doesn't look updated or missing, please consider checking the task in the Queued Tasks page in Indeavor and check the Job's Execution XML file.
Queued Tasks-> click on the eye icon for the run you want to check -> select "click here to view the result of the job's execution"
Reference the table below to understand what is causing the fail and the action required to resolve it. In case you need further assistance please reach out to support@indeavor.com
|
Interface |
Message |
Cause |
Action Required |
|
Employee Demographics Interface |
No active organizational unit is set |
Employee that doesn't exist in Indeavor is sent without an OU |
Resend employee with OU information included |
|
Validation failed ApprovedLeavesAction/RequestedLeavesAction/CancellationRequestedLeavesAction/VolunteeringsAction/KeepPrevious is required |
Existing employee sent with OU but without necessary transfer fields |
Resend employee with transfer fields or without any OU information |
|
|
Can not import new inactive employee |
Employee that does not exist in Indeavor is sent as inactive |
Verify that employee is inactive in source system |
|
|
Invalid id - code specified [OrganizationalUnit] |
OU is either mapped incorrectly or being sent incorrectly |
Ensure that OU is mapped correctly in Indeavor and that OU is being sent as expected from source system |
|
|
Invalid id - code specified [Role] |
Employee role is either mapped incorrectly or being sent incorrectly |
Correct format: Role_Employee |
|
|
Invalid id - code specified [Attribute] |
Attribute is either mapped incorrectly or being sent incorrectly |
Correct format: see functional specs; identify which attribute(s) don't match |
|
|
Updates not supported for inactive employee |
Attempting to update an employee that is inactive |
Verify if employee should be active in Indeavor |
|
|
Leave Balance Interface |
Invalid id - code specified [LeaveType] |
Leave type mapping in Indeavor does not match accrual code sent in import |
Add/Update Indeavor leave type Entity Mapping to match accrual code |
|
Invalid id - code specified [Employee] |
Leave sent for an employee that does not exist in Indeavor |
Verify if employee should exist in Indeavor |
|
|
Invalid id - code specified [AccountingPeriod] |
Accounting period mapping in Indeavor does not match accounting period sent in import |
Add/Update Indeavor accounting period Entity Mapping to match accounting period in import or verify that correct Accounting Period is being sent in import |
|
|
Specified employee, leave type and accounting period combination is not allowed. |
Employee, leave type, and accounting period do not share a common Organizational Unit on the effective date of the balance |
Include employee's primary OU in leave type configuration and accounting period configuration as of effective date |
|
|
Effective date should fall inside accounting period. |
Effective date of the balance falls outside of accounting period date range |
Adjust accounting period date range or send balance to an accounting period that the effective date is within |
|
|
Leave Request Interface |
Invalid id - code specified [LeaveType] |
Leave type mapping in Indeavor does not match leave type sent in import |
Add/Update Indeavor leave type Entity Mapping to match leave type in import |
|
Invalid id - code specified [Employee] |
Leave sent for an employee that does not exist in Indeavor |
Verify if employee should exist in Indeavor |
|
|
Invalid id - code specified [AccountingPeriod] |
Accounting period mapping in Indeavor does not match accounting period sent in import |
Add/Update Indeavor accounting period Entity Mapping to match accounting period in import or verify that correct Accounting Period is being sent in import |
|
|
Granting multiple leaves with overlapping time is not allowed |
Interface is trying to overwrite all or part of an existing leave in the system with --existing leave remains in place, new leave fails |
Possible solutions:
A. If existing leave is correct, determine why new leave is being sent from source system |
|
|
Item consists of entities which do not have common organizational units |
Employee is Inactive & Orphan (no OU assigned) OR employee, leave type, and accounting period do not share a common Organizational Unit on the effective date of the balance |
Possible solutions:
|
|
|
Granting multiple leaves with same leave type and overlapping periods is not allowed |
Interface is trying to overwrite all or part of an existing leave--existing leave remains in place, new leave fails |
Possible solutions:
A. If existing leave is correct, determine why new leave is being sent from source system |
|
|
Constraint violation occured XYZ is not valid for the assigned period, Assignment does not fully cover requirements expressed by XYZ post for the assigned period |
Error due to a Leave that is replacing an assignment that was breaking some constraints |
Check constraint configuration |
|
|
EmployeeLeaveRequest Not Exists |
Interface is trying to delete a leave that either does not exist or is not mapped |
Determine why leave in source system does not match what is in Indeavor |
|
|
The DateTime represented by the string is not supported in calendar System.Globalization.GregorianCalendar. |
Error due to the incorrect time format sent by the external interface |
eg.: <Field name="LeaveEndDate" value="2022-11-22T24:00:00"/> replaced with <Field name="LeaveEndDate" value="2022-11-23T00:00:00"/> |
|
|
Employee doesn't exists. For new leave reaquest's please set the Employee or LeaveType to use local time |
Employee and leave type do not share a common OU as of the date of the leave |
Include employee's primary OU in leave type configuration as of the date of the leave |
|
|
The accountable units of a leave cannot be 0 |
No base schedule assigned to employee on date of leave OR no shift preference assigned in employee base schedule on date of leave |
Update base schedule assignment or base schedule preference if necessary; this is sometimes intentionally done for RDOs |
|
|
The leave is not fully contained in the time span defined by the accounting period |
Effective date of the leave falls outside of accounting period date range |
Adjust accounting period date range or send leave to an accounting period that the effective date is within |
|
|
Overtime Balance Interface |
Invalid id - code specified [Employee] |
Overtime balance sent for an employee that does not exist in Indeavor |
Verify if employee should exist in Indeavor |
|
Invalid id - code specified [Aggregate] |
Aggregate mapping in Indeavor does not match aggregate sent in import |
Add/Update Indeavor aggregate Entity Mapping to match aggregate in import |
|
|
Invalid id - code specified [ChargeBucket] |
Charge bucket mapping in Indeavor does not match charge bucket sent in import |
Add/Update Indeavor charge bucket Entity Mapping to match charge bucket in import |
|
|
The aggregate and the target value is equal |
Aggregate’s current value and value sent by the import are equal. So there is no change |
No action required |
|
|
Demand Creation Interface (Classic) |
Invalid id - code specified [Template] |
Labor Demand Template mapping in Indeavor does not match aggregate sent in import |
Add/Update Indeavor Labor Demand Template Entity Mapping to match import |
|
Invalid id - code specified [Location] |
Location mapping in Indeavor does not match aggregate sent in import |
Add/Update Indeavor location Entity Mapping to match location in import |
|
|
Invalid id - code specified [DemandCategory] |
Demand Category mapping in Indeavor does not match aggregate sent in import |
Add/Update Indeavor Demand Category Entity Mapping to match Demand Category in import |
|
|
Invalid id - code specified [OrganizationUnit] |
Organizational Unit mapping in Indeavor does not match aggregate sent in import |
Add/Update Indeavor Organizational Unit Entity Mapping to match Organizational Unit in import |
|
|
Item consists of entities which do not have common organizational units |
Labor Demand Template, Location, Demand Category, and/or Organizational Unit do not share a common OU as of the date of the imported demand |
Ensure that at least one common OU exists between all imported entities as of the date of the demand |
|
|
Employee Qualifications Import (New) |
System.Exception: No Employee found with mapping '<submitted ID>' |
Employee ID or Mapping submitted not found within Indeavor |
Confirm fieldType submitted is correct |
|
System.Exception: No Skill found with mapping '<submitted ID>' |
Qualification/Skill ID or Mapping submitted not found within Indeavor |
Confirm fieldType submitted is correct |
|
|
Validation failed: -- x[0].ValidTo: 'Valid To' must be greater than '<dateTime>'. |
ValidFrom is set to after ValidTo |
Confirm ValidFrom is set to before ValidTo if both dates are included in request |
|
|
The JSON value could not be converted to Indeavor.Skills.Common.Dtos.EmployeeSkills.Requests.EmployeeSkillImportRequestEntry. Path: $.Entries.<employeeID>[0].<fieldName> |
The value sent for the specified field and employee is not valid. |
For CompetencyLevel, ensure the value is an integer, 1-5. If default competency level or no competencylevel is desired, omit entire field, not only the value. |