Before Arcoro sends an employee to Sage 300 CRE through HH2, it checks a few basic facts about that employee. Sage 300 CRE will not accept an employee record that has no hire date, and it will not accept a hire date that falls in the future. HH2 also will not let Arcoro update an employee that has been marked archived on the HH2 side. When any of these checks fail, Arcoro stops that one employee from being written to HH2 for the current sync, rather than sending data Sage 300 CRE cannot use.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The matching employee in HH2 has IsArchived = true and the Sync process cannot update it. To Sync this employee contact Arcoro support to have HH2 set IsArchived = false for the employee and run the Sync again. | Write (Arcoro to Sage 300 CRE via HH2) | The employee identifier Arcoro is about to send matches an employee code that HH2 reported as archived when Arcoro loaded the company's employee list at the start of the sync. | Record skipped. The employee is not written to HH2 for this run. | Escalate so HH2 can be updated. See When to escalate below. |
| The hire date should be specified. This employee will not be synced in HH2. | Write (Arcoro to Sage 300 CRE via HH2) | The employee record has no hire date at all. | Record skipped. The employee is not written to HH2 for this run. | Enter a hire date on the employee's profile in the Arcoro platform, then run the sync again. |
| Future Hire Dates are not supported by Sage 300 CRE. | Write (Arcoro to Sage 300 CRE via HH2) | In practice, this exact message should not appear. Its underlying check only runs when the hire date is both blank and dated tomorrow or later at the same time, which cannot both be true for the same employee. See How to confirm below for what to do if you see it anyway. | Record skipped, if it were to occur. | Do not treat this as a normal hire-date fix. Escalate to engineering as a possible defect. |
| Future Hire Dates are not supported by Sage 300 CRE. This employee will not be updated in HH2. | Write (Arcoro to Sage 300 CRE via HH2) | The employee has a hire date, and that hire date falls tomorrow or later, measured from today's date at the start of the sync. A hire date of today or earlier does not trigger this message. | Record skipped. The employee is not written to HH2 for this run. | Correct the hire date on the employee's profile in the Arcoro platform so it is today's date or earlier, then run the sync again. |
Confirming the Error
- Open the Sync History screen for the sync execution in question.
- Find the step for the Sage 300 CRE connector in that execution.
- Locate the row for the People or Employees entity in that step. The row shows counts for Errors, Warnings, Information, Failures, Added, Updated, and Unchanged.
- If the Errors count is greater than zero, open that entity row and find the specific employee in question.
- Open the errors list for that employee and match on the fixed part of the sentence, not on the values in quotes or on any employee-specific text.
The archived employee message is logged as an Error, not a Warning, even though its internal name suggests otherwise. Look for it in the Errors count, not the Warnings count.
Telling the two future hire date messages apart: The message that reads "Future Hire Dates are not supported by Sage 300 CRE." with nothing after it is not expected to appear in a live sync log, because the condition that would trigger it cannot occur. The message that reads "Future Hire Dates are not supported by Sage 300 CRE. This employee will not be updated in HH2." with the second sentence is the one you will normally see for a future-dated hire. If your log genuinely shows the shorter, one-sentence version, do not try to fix it as a normal hire date issue. Copy the full message text and escalate it to engineering as unexpected behavior.
These checks do not short-circuit each other. Every check runs on every sync attempt for that employee, so all of the applicable messages in this family, and any other employee validation messages, appear together in the same sync run. Fixing everything currently shown in the errors list and running the sync again should be enough. You should not expect a message from this family to stay hidden and only appear after another one is fixed.
Resolving the Error
Employee is Archived in HH2
- Confirm the employee identifier shown in the error matches the employee.
- This one cannot be fixed from the Arcoro platform side. Follow the steps in When to escalate below.
- Once HH2 has been updated, run the sync again for this connector.
- Confirm the fix by checking the Sync History screen again. The employee's row should show an Add or Update count instead of an Error count.
Hire Date is Missing
- In the Arcoro platform, open the employee's profile.
- Enter a hire date for the employee.
- Save the change.
- Run the sync again for this connector.
- Confirm the fix by checking the Sync History screen. The employee's row should show an Add or Update count and the Errors count for this employee should be gone.
Hire Date Is in the Future
- In the Arcoro platform, open the employee's profile.
- Check the hire date field. If it is dated tomorrow or later, correct it to the employee's actual hire date.
- Save the change.
- Run the sync again for this connector.
- Confirm the fix by checking the Sync History screen. The employee's row should show an Add or Update count and the Errors count for this employee should be gone.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The employee is reported as archived in HH2. Gather the connector or company name, the employee identifier, and the sync execution date and time, then escalate the request to have HH2 set the employee's archived flag back to false.
- Your log shows the one-sentence message "Future Hire Dates are not supported by Sage 300 CRE." with no second sentence. This should not occur under normal conditions. Copy the exact message, the employee identifier, and the sync execution date and time, and escalate to engineering as unexpected behavior.
- The hire date on the employee's profile already looks correct (present and not in the future) but the error persists after a rerun. Escalate with the employee identifier and a screenshot or export of the current hire date value.