Problem: Indeavor is aware of an issue where new future dated employees are not created via the Employee Updates Import.
- For customers that send delta files, new employee updates are sent only when the employee is added. The employee and associated user must be manually created in Indeavor. After they are created ensure there is an Entity mapping, this will ensure they are associated with the source system for future updates after this issue is resolved.
-
- Please keep in mind when creating a User, it is important to give them the correct role at the OU (Typically, the correct role is Employee-Indeavor at the OU level)
-
- For customers that send full files the employee will be available after the employee's start date or the employee must be manually created in Indeavor. After they are created ensure there is an Entity mapping, this will ensure they are associated with the source system for future updates after this issue is resolved.
-
Update 12/20/2024 - We are also aware of an issue where inactivated employees are not removed via the import. For employees that are not inactivated via the import, you will need to manually inactivate those employees in Indeavor.
-
- The correct process for manually inactivating an employee is adding the "valid to" date in their OU association and then inactivating the employee. Following this workflow should correctly inactivate both the employee and their associated user.
-
If you need assistance in identifying the employees affected.
- Go to Queued Tasks
- Click on the eye to the result's of the job execution
- Look for the error message: "There are intervals in the future without a primary OU. Please enter them before proceeding with the action"
Our technical team is working on a fix.
If you have any issues manually creating or inactivating an employee, please submit a support ticket to support@indeavor.com so that our Service Center can assist you.