Union and Labor Classification records both need a Name, and that Name has to be unique within a single run of the sync. Payroll checks this from two directions. When Payroll is the source, it checks the Name as each Union record is read out. When Payroll is the destination, it checks the Name again as each Union or Labor Classification record is about to be written in. Either way, a missing or repeated Name stops that one record without stopping the rest of the sync.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Union Name is a required field. | Read, Payroll is the source | The Union record's Name is blank or all whitespace when it is read out of Payroll. | Record skipped. The Union is not passed on to the rest of the sync. | In Payroll, add a Name to the Union record, then run the sync again. |
| Union '[union name]' has been sent to Payroll multiple times. Only the first Union with this name will be saved. Correct the source data and run the sync again. | Write, Payroll is the destination | Two or more Union records in the same sync run have the same Name (matched without regard to upper or lower case), after each has already passed its own required-Name check. | Record skipped for every Union after the first with that Name. The first Union with that Name in the run is still saved. | In the source system feeding this sync, rename the duplicate Unions so each Name is unique, then run the sync again. |
| A Labor Classification with Name: '[labor classification name]' has been sent to Payroll multiple times. Only the first Labor Classification with this Name will be saved. Correct the source data and run the sync again. | Write, Payroll is the destination | Two or more Labor Classification records in the same sync run have the same Name (matched without regard to upper or lower case), after each has already passed its own required-Name check. | Record skipped for every Labor Classification after the first with that Name. The first Labor Classification with that Name in the run is still saved. | In the source system feeding this sync, rename the duplicate Labor Classifications so each Name is unique, then run the sync again. |
Confirming the Error
- Open the sync execution for the run in question.
- Find the step for the Payroll connector.
- Find the Union row or the Labor Classification row for that step.
- Check the Errors column for that row. All three messages in this article are logged as errors, not warnings or failures, so they show up in the Errors count.
- Open the errors list for that row and match on the fixed part of the sentence, ignoring the value inside the quotes.
- If the errors list instead shows the text "A record with Name: '[name]' has already been read. This field must be unique and the record will not be Synced. Modify the data in Payroll to make each record have a unique Name and execute the Sync again.", that message belongs to the org structure article, not this one. It also fires on the Union entity, but for a different reason. See payroll-org.html.
- A non-zero Failures count on the Union or Labor Classification row is not caused by any of the three messages in this article. Treat a Failures count as a separate issue.
Resolving the Error
Union Name Is a Required Field
- In Payroll, open the Union record named in the sync log entry's identifier.
- Enter a Name for the Union and save the record.
- Run the sync again.
- Confirm the Union no longer appears in the Errors list for that entity.
Union Sent to Payroll Multiple Times
- Identify the source system configured for this sync connector.
- In that source system, find every Union record with the Name quoted in the message.
- Rename all but one of them so every Union Name is unique.
- Run the sync again.
- Confirm the Union no longer appears in the Errors list, and that the Union you renamed now shows with its new Name.
Labor Classification Sent to Payroll Multiple Times
- Identify the source system configured for this sync connector.
- In that source system, find every Labor Classification record with the Name quoted in the message.
- Rename all but one of them so every Labor Classification Name is unique.
- Run the sync again.
- Confirm the Labor Classification no longer appears in the Errors list, and that the record you renamed now shows with its new Name.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The error is still there after confirming every Name is unique and none are blank, and you have already run the sync again.
- The message text in the log does not match the fixed part of any message in the table above.
- The row shows a non-zero Failures count for the Union or Labor Classification entity.
- The text in the errors list looks like it came from your own ERP or Payroll system rather than from an Arcoro message, for example wording that does not match anything in this article.