Sage 100 Construction requires an Occupation and a Workers Compensation Code on every employee before Arcoro can update that employee in Sage 100. If either field is empty in Arcoro, the employee is not sent to Sage 100 at all.
Separately, when Arcoro reads the list of Employment Positions from Sage 100 to build the Occupation list, two positions with the exact same name cannot both come across. Arcoro keeps the first one it processes and drops every later one with the same name. This is a different problem from the two employee messages above: it is about the Occupation lookup list itself, not about any one employee's data.
A similar duplicate-name situation exists for Union records read from Sage 100. That is covered in a separate article and is not repeated here.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Occupation is required. | Arcoro to Sage 100 (write) | The employee's Occupation field is blank, empty, or only whitespace in Arcoro. | Whole employee record skipped. The employee is not written to Sage 100 on this sync. | Enter an Occupation on the employee's record in Arcoro. |
| Work Compensation Code is required by Sage 100 Construction. This employee will not be updated in HH2. | Arcoro to Sage 100 (write) | The employee's Workers Compensation Code field is blank, empty, or only whitespace in Arcoro. | Whole employee record skipped. The employee is not written to Sage 100 on this sync. | Enter a Workers Compensation Code on the employee's record in Arcoro. |
| Duplicate Name read from HH2 EmploymentPosition. Duplicate will not be used. | Sage 100 to Arcoro (read) | Two or more Employment Position records in Sage 100 share the exact same Name (the comparison is case sensitive, so "Carpenter" and "carpenter" would count as different). Archived Employment Position records are excluded before this check runs, so an archived record never triggers this and never appears anywhere in the log. Positions are read in parallel, so which one is kept and which one is flagged as the duplicate is not predictable from run to run. | Collection item skipped. Only the duplicate Employment Position record is skipped; it is not created or updated as an Occupation in Arcoro. The other position keeps that name. | In Sage 100 Construction, rename or archive one of the Employment Position records so no two active positions share the same Name. |
Confirming the Error
- Open the sync execution in the Sync History screen for the date and time in question.
- Find the step for the Sage 100 connector.
- For the two employee messages, open the Employees entity row for that step and check its Errors column. A non-zero count means at least one employee has a validation error.
- For the duplicate Occupation message, open the Occupation entity row for that step instead. This is a separate row from Employees, because Occupation is read from Sage 100 as its own lookup entity. Check its Errors column.
- Open the errors list for the relevant entity row and match on the fixed part of the sentence, not on any value in quotes. All three messages in this article have no variable text, so the full text is the match.
- If more than one of the two employee messages appears against the same employee, that is expected. Both required-field checks run every time, so an employee missing both Occupation and Workers Compensation Code gets both messages in the same pass.
- A non-zero Failures count on either entity row is not related to any message in this article. None of these three messages stop the sync; Failures reflects a different kind of problem and should be treated separately.
Resolving the Error
Occupation is Required
- In Arcoro, open the employee's record and set the Occupation field to a value.
- Save the employee record.
- Re-run the sync and confirm the employee no longer appears in the Employees entity's errors list.
Work Compensation Code is Required
- In Arcoro, open the employee's record and set the Workers Compensation Code field to a value.
- Save the employee record.
- Re-run the sync and confirm the employee no longer appears in the Employees entity's errors list.
Duplicate Name Read from HH2 EmploymentPosition
- In Sage 100 Construction, find the two (or more) Employment Position records that share the same Name.
- Rename one of them to a unique value, or archive the one that is no longer in use.
- Re-run the sync and confirm the Occupation entity's errors list no longer shows the duplicate for that name.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- An employee still shows one of the two required-field messages after the Occupation or Workers Compensation Code field was confirmed populated in Arcoro and saved.
- The duplicate Occupation message persists after you renamed or archived one of the Employment Position records in Sage 100.
- The log text does not match any of the three messages in this article word for word.
- The same employee or Occupation record swaps back and forth between being written and being skipped across consecutive syncs with no source data change, since this points to a data or timing issue beyond a simple missing field.