Sage 100 will not accept an employee unless Employee Status, Employee Type, and Hire Date are all present and Hire Date is not in the future. This connector also uses Employee Status and Employee Type in a swapped way behind the scenes: the employee's Employee Status value is matched against Sage 100's list of Employee Types, and the employee's Employee Type value is matched against Sage 100's list of Employee Statuses. Because of that swap, a message that says "Employee Type could not be mapped" is actually complaining about the Employee Status value, and a message that says "Employee Status could not be mapped" is actually complaining about the Employee Type value. Separately, one message in this family has nothing to do with an individual employee at all: it occurs while Arcoro is reading Sage 100's own Employee Status list to build a reference list, and it means one entry in that list is missing a code.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Employee Status is required. | Arcoro to Sage 100 (write) | The employee's Employee Status field is empty, or is set to the undefined/blank status option. | Whole employee record skipped for this sync. | Set a valid Employee Status (Full-Time, Part-Time, Terminated, Retired, or On Leave) on the employee in the source system. |
| Employee Type is required. | Arcoro to Sage 100 (write) | The employee's Employee Type field is blank or contains only whitespace. | Whole employee record skipped for this sync. | Set an Employee Type value on the employee in the source system. |
| The hire date should be specified. This employee will not be synced in HH2. | Arcoro to Sage 100 (write) | The employee has no Hire Date value at all. | Whole employee record skipped for this sync. | Enter a Hire Date for the employee in the source system. |
| Future Hire Dates are not supported by Sage 100 Construction. This employee will not be updated in HH2. | Arcoro to Sage 100 (write) | The employee has a Hire Date value, and that date falls on or after tomorrow (compared in UTC). This check only runs when a Hire Date is present, so an employee cannot trigger this message and the previous one in the same sync attempt. | Whole employee record skipped for this sync. | Correct the Hire Date to today or an earlier date. If the hire genuinely has not happened yet, wait until the date arrives before running the sync again. |
| Employee Type '[Employee Status value]' could not be mapped. The employee will not be synced to HH2. Correct the data and run the sync again. | Arcoro to Sage 100 (write) | Despite the wording, this is driven by the employee's Employee Status value, not the Employee Type field. Only a status of Full-Time or Part-Time is converted, to the exact text "Full-Time" or "Part-Time", and matched (case-sensitive, exact match) against Sage 100's list of Employee Types. Any other status value (Terminated, Retired, or On Leave) is never looked up at all and always fails this check. | Whole employee record skipped for this sync. | See How to resolve below. The fix depends on which status the employee has. |
| Employee Status '[Employee Type value]' could not be mapped. The employee will not be synced to HH2. Correct the data and run the sync again. | Arcoro to Sage 100 (write) | Despite the wording, this is driven by the employee's Employee Type value, not the Employee Status field. The exact text in the employee's Employee Type field is matched (case-sensitive, exact match) against the Name of a record in Sage 100's list of Employee Statuses. | Whole employee record skipped for this sync. | Correct the Employee Type text in the source system so it exactly matches a status name in Sage 100's Employee Status list, or add/rename that status in Sage 100. |
| The employee type does not have a valid code and will not be synced. | Sage 100 to Arcoro (read) | This occurs while Arcoro reads Sage 100's Employee Status list to build the Employee Types reference list, not while processing an individual employee. It occurs for any non-archived Sage 100 Employee Status record whose Code field is blank or whitespace only. | That one Employee Status record is left out of the Employee Types list in Arcoro. Other records in the list are still read normally. | In Sage 100, open the affected Employee Status record and give it a Code, then re-run the read. |
Confirming the Error
- Open the sync execution in Sync History for the date and connector in question.
- For the six employee messages, find the Employees row for the write step of that execution.
- For the Employee Types message, find the Employee Types row for the read step instead.
- Open the Errors list for that row. The Sync History screen shows per-entity counts labelled Errors, Warnings, Information, Failures, Added, Updated, and Unchanged; all seven messages in this article are logged as Errors, not Failures.
- Match on the fixed part of the sentence, not on the value inside the quotes, since that value is the your data and will vary.
- A non-zero Failures count on the Employees or Employee Types row points to a different problem than the ones in this article; treat it separately.
Resolving the Error
Employee Status is Required / Employee Type is Required
- In the source system, open the employee record that appears in the error.
- Set the Employee Status field (or Employee Type field) to a valid value.
- Re-run the sync and confirm the employee no longer appears in the Employees row's Errors list.
Hire Date Messages
- In the source system, open the employee record.
- Enter a Hire Date if one is missing, or correct it so it is today's date or earlier if it was rejected as a future date.
- Re-run the sync and confirm the employee moves out of the Errors list.
Employee Type ‘[Value]’ Could Not Be Mapped
- Check the employee's Employee Status value in the source system.
- If the status is Full-Time or Part-Time, open Sage 100's Employee Type list and confirm there is an Employee Type named exactly "Full-Time" or "Part-Time" (matching spelling, spacing, and capitalization). Create or rename an Employee Type if needed.
- If the status is Terminated, Retired, or On Leave, this message will always occur for that employee; there is no Sage 100 Employee Type setup that resolves it. Escalate rather than continuing to adjust Sage 100 data.
- Re-run the sync and confirm the employee moves out of the Errors list.
Employee Status ‘[Value]’ Could Not Be Mapped
- Note the exact Employee Type text shown in the error.
- In Sage 100, open the Employee Status list and look for a status whose name matches that text exactly, including capitalization.
- Correct the Employee Type value in the source system to match an existing Sage 100 status name, or add/rename a Sage 100 status so it matches.
- Re-run the sync and confirm the employee moves out of the Errors list.
The Employee Type Does Not Have a Valid Code and Will Not Be Synced
- In Sage 100, open the Employee Status list.
- Find the status named in the error's identifier and add a Code value to it.
- Re-run the sync and confirm the record now appears in the Employee Types row instead of its Errors list.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The employee's Employee Status is Terminated, Retired, or On Leave and the message is "Employee Type could not be mapped". No Sage 100 configuration change resolves this; escalate to confirm whether the source data should be sending a different status or a different signal for termination.
- The error persists after the source data and the Sage 100 Employee Type or Employee Status list have both been checked and appear to match.
- The message text in the log does not match any row in the table above.
- The Failures count on the Employees or Employee Types row is non-zero.