Module Navigation

Troubleshooting CMiC Integration Error: Employment Status, Hire and Termination Dates

CMiC keeps a running history of each employee, not just a single current record. When Arcoro creates a brand new employee in CMiC, it uses the employee's Hire Date as the starting point of that history, so CMiC has to receive a valid hire date before it will accept the employee at all. CMiC also only understands a small, fixed set of employee status values, so the employee's status in Arcoro has to be set to one of the values CMiC recognizes. When an employee's status is Terminated, CMiC additionally needs a termination date, and that termination date has to fall on or after the employee's hire date (or rehire date, if the employee was rehired), so the employee's timeline inside CMiC stays in the correct order. If any of this information is missing or out of order, Arcoro holds the employee back from this sync run rather than send CMiC a record it cannot place correctly in its history.

Error Messages

Message textDirectionOccurs whenOutcomeFix
Employee Hire Date is required. Employee will not be sent to CMiC.Write (Arcoro to CMiC)The employee's Hire Date field is blank.Whole employee record is skipped.Enter a Hire Date on the employee's record in Arcoro.
Employee Status is required. Employee will not be sent to CMiC.Write (Arcoro to CMiC)The employee's status value is blank.Whole employee record is skipped.Set an employee status value on the employee's record in Arcoro.
A match for employee status '[employee status value]' was not found in CMiC. The employee will not be processed. Correct the data and run the sync again.Write (Arcoro to CMiC)The employee's status value is present, but it does not match one of the status names Arcoro recognizes for CMiC (Active, Terminated, or Deceased, optionally followed by a sub-status, for example Active-Working). The match is exact and case sensitive.Whole employee record is skipped.Correct the employee's status value in Arcoro so it reads exactly Active, Terminated, or Deceased, matching upper and lower case.
The employee '[employee id]' has a terminated status, but is missing a termination date. Correct the data in the source system and run the sync again.Write (Arcoro to CMiC)The employee's status is Terminated in Arcoro, but the Termination Date field is blank.Whole employee record is skipped.Enter a Termination Date on the employee's record in Arcoro.
Employee '[employee id]' has a terminated status, but the termination date is older than its Hire/Original Hire Date. Review the data o the source system and run sync again.Write (Arcoro to CMiC)The employee's status is Terminated in Arcoro, and the Termination Date is earlier than the employee's Hire Date, or earlier than the Rehire Date if the employee has one.Whole employee record is skipped.Correct the Hire Date, Rehire Date, or Termination Date in Arcoro so the termination date falls on or after both.

Note: the last message text has a typo in the source system ("data o the source system" instead of "data on the source system"). Reproduce it exactly if you are quoting the log back to us or in a ticket, so anyone string matching the log can find it.

Confirming the Error

  1. Open Sync History and find the sync execution for the run in question.
  2. Open the step for the CMiC connector.
  3. Find the Employees entity row for that step. Check the Errors column; a nonzero count here means at least one employee had a validation problem on this run.
  4. Open the errors list for the Employees entity row.
  5. Search for the employee by their employee id or name, then match each message against the fixed part of the sentence (for example, "Employee Hire Date is required"), not against the quoted values, since quoted values change per employee.
  6. Read every message listed for that employee. These checks all run together, so one employee can show two or more of these messages on the same errors list at once.

Resolving the Error

Employee Hire Date is Required

  1. In Arcoro, open the employee's record in the source HR product feeding this sync.
  2. Enter a Hire Date for the employee.
  3. Save the record.
  4. Run the sync again and confirm the Hire Date error no longer appears on the Employees entity's errors list.

Employee Status is required, or does not match CMiC

  1. In Arcoro, open the employee's record and locate their employee status field.
  2. Set the status to exactly Active, Terminated, or Deceased, matching upper and lower case. A sub-status may follow, separated by a hyphen, for example, Active-Working.
  3. Save the record.
  4. Run the sync again and confirm the status error no longer appears for that employee.

Terminated Employee Is Missing a Termination Date

  1. In Arcoro, open the employee's record and confirm the status is intentionally set to Terminated.
  2. Enter the employee's Termination Date.
  3. Save the record.
  4. Run the sync again and confirm the missing termination date error no longer appears for that employee.

Termination Date Is Older Than the Hire Date

  1. In Arcoro, open the employee's record and review the Hire Date, Rehire Date (if the employee was rehired), and Termination Date together.
  2. Correct whichever date is wrong so the Termination Date falls on or after the Hire Date and, if present, the Rehire Date.
  3. Save the record.
  4. Run the sync again and confirm this error no longer appears for that employee.

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

  • You confirm the Hire Date, employee status, and termination date all look correct in Arcoro, but the same error keeps appearing after a resync.
  • The employee's status value already reads exactly Active, Terminated, or Deceased, matching case, and the employee still gets the status mismatch message.
  • Correcting the Hire Date, Rehire Date, and Termination Date in Arcoro does not clear the termination-date-older-than-hire message on the next run. Escalate with the employee id and the before-and-after values of all three dates.
Was this article helpful?
0 out of 0 found this helpful