These two messages both come from the Labor Classification read, which pulls Class records out of Sage Intacct into Arcoro. Because this is a read, the bad data and the fix both live in Sage Intacct, not in Arcoro. The message wording talks about modifying "the data," which can sound like an Arcoro instruction. It is not. The record only exists in Sage Intacct, so that is where you must make the change. One message fires when a Class record has no Name value. The other fires when two Class records resolve to the same ID and Name combination. Either way, Arcoro leaves that one record out and continues reading the rest.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Name field is required and the record will not be Synced. Modify the data to make each record have a unique Name and execute the Sync again. | Read (Sage Intacct to Arcoro). Labor Classification only. | The Class record's Name field is blank, empty, or only whitespace in Sage Intacct. | Record skipped. Only this Class record is left out; every other Labor Classification record continues to be read. | In Sage Intacct, enter a Name on the Class record, then run the sync again. |
| A Labor Classification has already been read with this ID and Name properties. The combination of these fields must be unique and the record will not be Synced. Modify the data to make each record have a unique Id and Name combination and execute the Sync again. | Read (Sage Intacct to Arcoro). Labor Classification only. | A Class record's ID and Name, joined together, match a combination already read earlier in the same sync. The comparison ignores upper and lower case, so records that differ only by letter case still count as the same combination. The ID and Name are joined with a fixed separator before comparing, so two records with different ID and Name values individually can still produce the same joined text and be treated as duplicates. | Record skipped. Only the later duplicate is dropped; the first record with that combination is kept and synced normally. Every other Labor Classification record continues to be read. | In Sage Intacct, give the Class record a unique ID and Name combination, treating upper and lower case as identical, then run the sync again. |
Confirming the Error
- Open the sync execution in question.
- Find the step for the Sage Intacct connector.
- Find the Labor Classification entity row. Sync History shows per-entity counts in columns labelled Errors, Warnings, Information, Failures, Added, Updated, and Unchanged. A non-zero Errors count means one or more Class records were skipped.
- Open the errors list for that entity row and match the entry against the exact wording in the table above. Neither message contains a quoted or inserted value, so there is no variable text to search for.
- Opening the entity row is the only way to see which record the message belongs to; the label shown there is built from the record's ID, Name, and Description as read from Sage Intacct.
Resolving the Error
Both fixes happen in Sage Intacct, on the ID and Name fields of the Class record.
The Name Field is Required
- In Sage Intacct, open the Class record identified in the errors list.
- Enter a value in the Name field. It cannot be blank or only spaces.
- Save the record.
- Run the sync again and confirm the record no longer appears in the Labor Classification errors list.
Duplicate ID and Name Combination
- In Sage Intacct, open the two Class records that share the same ID and Name combination.
- Change the ID or the Name on one record so the combination is unique. A change in letter case alone does not make it unique.
- Save the record.
- Run the sync again and confirm the record no longer appears in the Labor Classification errors list.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The ID and Name are already unique. The comparison ignores letter case and joins ID and Name together before comparing, so two records that look different, such as differing only by case, or differing in where the ID ends and the Name begins, can still collide.
- The error persists after the Sage Intacct record has been corrected and the sync re-run.
- The log text does not match either message in the table above.
- The Labor Classification records are missing from Arcoro, but the errors list for that entity is empty. That points to something outside these two messages and needs investigation.