Sage 300 CRE stores two fields on every union, union local, and union class record: a short Code and a longer Description. This connector has a setup option called Key Unions By Code that tells Arcoro which of those two fields to treat as the record's identifier. When that option is turned on and the Code field is blank, Arcoro cannot read the record at all, even though the on screen message talks about a missing Description. When the option is off, a blank Description only produces a warning, and Arcoro falls back to using the Code instead.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Union with Name '[union description or blank]' does not have a valid Description and will not be read. Correct the data and run the sync again. | Read (Sage 300 CRE into Arcoro) | Key Unions By Code is turned on for this connector, and the Code field on that Union record in Sage 300 CRE is blank or whitespace. The message names Description, but the field Arcoro actually checked is Code. | Record skipped. This Union is not added or updated in Arcoro. | In Sage 300 CRE, enter a Code value on the flagged Union record. |
| Union Local with Name '[union local description or blank]' does not have a valid Description and will not be read. Correct the data and run the sync again. | Read (Sage 300 CRE into Arcoro) | Key Unions By Code is turned on for this connector, and the Code field on that Union Local record in Sage 300 CRE is blank or whitespace. The message names Description, but the field Arcoro actually checked is Code. | Record skipped. This Union Local is not added or updated in Arcoro. | In Sage 300 CRE, enter a Code value on the flagged Union Local record. |
| Union Class with Name '[union class description or blank]' does not have a valid Description and will not be read. Correct the data and run the sync again. | Read (Sage 300 CRE into Arcoro) | Key Unions By Code is turned on for this connector, and the Code field on that Union Class record in Sage 300 CRE is blank or whitespace. The message names Description, but the field Arcoro actually checked is Code. | Record skipped. This Union Class is not added or updated in Arcoro. | In Sage 300 CRE, enter a Code value on the flagged Union Class record. |
Confirming the Error
- Open the sync run in the Arcoro sync history for this connector.
- Find the Company section and open the entity row named Unions, Union Locals, or Union Classes, matching whichever message was reported.
- Check the Errors column for that entity row. A count above zero, together with an Added, Updated, and Unchanged count that looks lower than expected, matches this issue.
- Open the entity detail and look for a message that starts with "Union with Name", "Union Local with Name", or "Union Class with Name" and ends with "does not have a valid Description and will not be read." Match on this fixed part of the sentence, not on the value shown in quotes, since that value can be blank.
- If the row's own name or identifier column is blank in the log, that is expected here. It happens because Arcoro was told to key this record by its Code, and the Code is the field that is empty.
- Confirm this is an Error, not a Warning. A Warning with text about a Code being used instead of an empty Name property is a different, non blocking condition and is not covered by this article.
Resolving the Error
All three record types resolve the same way. The field you must fix is Code, not Description, regardless of what the message text says.
If Key Unions by Code Is off for This Connector
This error family cannot occur while this option is off. If you see this exact message, escalate.
If Key Unions by Code Is on for This Connector
- Confirm the Key Unions By Code setting on the connector configuration page.
- Open the matching setup screen in Sage 300 CRE for the record type named in the message, Union, Union Local, or Union Class, and enter a Code value for the flagged record.
- Re-run the sync for the Company domain, or for the full connector if that is their normal process.
- Reopen sync history and confirm the Errors count for the affected entity is now zero, and that the record now appears under Added or Updated.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- You confirm the Code field is filled in on the flagged record in Sage 300 CRE, but the same error still appears after a re-run.
- You report this exact message while Key Unions By Code is off on the connector configuration page, since this error cannot occur in that state.
- Several rows for the same entity show a blank name in the sync log and you cannot tell which Sage 300 CRE records they correspond to.
- You see Employee level preload errors mentioning a duplicate key for Unions, Union Locals, or Union Classes in the same run. That is a related but separate issue and should be escalated together with this one.