Overview
This article lists the errors the OroCommerce integration can record in the iPaaS.com error logs. Each error carries a stable code you can search for on this page (for example, OROC-VALD-1001), the message as it appears in the logs, why it occurs, and the steps to resolve it. Every OroCommerce integration error code has three segments — OROC, a category, and a number (for example, OROC-EXTN-1001); platform errors raised by the iPaaS.com API itself use two segments (for example, VALD-1002), so the number of segments tells you which catalog to look in.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
The OroCommerce integration can record errors in the following flows:
Product
Product Variant
Bulk Pricing (Price List)
Customer
Customer Group
Customer User
Order
Invoice
Shipping Tracking
Connection and Authentication
General and Identifier
Error Collection
Product
Kit component required
OROC-VALD-1013 - At least one product kit component is required for creating a KIT product.
Description: A kit product was sent without any kit components, which OroCommerce requires.
Resolution: Add at least one product kit component to the kit product in iPaaS.com, then re-transfer.
Kit type required
OROC-VALD-1014 - Product kit type is required for creating a KIT product.
Description: A kit product was sent without a kit type value.
Resolution: Populate the product kit type field for the kit product in iPaaS.com before re-transferring.
Product Id required for update
OROC-VALD-1015 - Product Id is required for Update.
Description: An update was attempted for a product that has no resolved OroCommerce ID.
Resolution: Confirm the product was created in OroCommerce first, so its external ID is stored in iPaaS.com, or run the record through the create operation rather than update.
Default pricing required values (product)
OROC-VALD-1016 - Default pricing {value} is required for creating a product.
Description: One or more required default-pricing values were missing when the product was created or updated. The specific value is named in the message — one of: type, attribute value, attribute quantity, attribute currency, the relationship price list id/type, or the relationship unit id/type.
Resolution: Populate the missing default-pricing mappings (type, value, quantity, currency, the price list ID and type, and the unit ID and type) so each required value resolves to a non-empty value, then re-transfer.
Default pricing price list name not resolved
OROC-BIZL-1020 - Product can not be created because incorrect price list name is provided through mappings for the default pricing creation.
Description: The default-pricing price list name supplied through the mappings did not resolve to a price list in OroCommerce, so the integration could not attach the product's default pricing. The update path reports the equivalent message ending "for the default pricing update."
Resolution: Confirm the price list name produced by the default-pricing mapping exactly matches an existing OroCommerce price list, then re-transfer.
Default pricing custom field not found
OROC-BIZL-1003 - The configured Default Pricing custom field "{field}" does not exist on the Product Price entity in OroCommerce.
Description: The default-pricing custom field name configured in the subscription settings does not match any field on the OroCommerce Product Price entity.
Resolution: Create a custom field on the Product Price entity in OroCommerce whose name exactly matches the configured Default Pricing custom field, or correct the configured name in the subscription settings.
Default pricing custom field is not boolean
OROC-BIZL-1004 - The configured Default Pricing custom field "{field}" exists on the Product Price entity in OroCommerce, but its type is "{type}". A boolean (bool) field is required.
Description: The default-pricing custom field exists but is not a boolean field.
Resolution: Recreate the Product Price custom field with a boolean (Yes/No) field type in OroCommerce, or point the configured Default Pricing custom field name at an existing boolean field.
Unsupported product type
OROC-BIZL-1001 - Unsupported product type: {type}
Description: The product being transferred has a product type value that the integration does not know how to create or update in OroCommerce.
Resolution: Set the product type to a value the integration supports (for example, a simple or kit product type) and confirm the value matches OroCommerce's expected casing before re-transferring.
Invalid match field
OROC-BIZL-1002 - Invalid match field: {field}
Description: A configured match field is not one the integration recognizes for locating an existing OroCommerce record. This applies to product matching and to order (transaction) matching.
Resolution: Set the match field mapping to a supported value (for example, SKU for products) and re-transfer.
Kit component product could not be transferred
OROC-BIZL-1017 - Unable to transfer kit component's product in HandlePrerequisite. This will prevent the transfer of this product (SKU: {sku}) as well.
Description: A kit product transfers its component products first; one of those component products could not be transferred, so the kit product transfer was stopped.
Resolution: Resolve the underlying component-product error, which is logged separately, confirm that product transfers on its own, then re-transfer the kit product.
Unable to read Product Price entity fields
OROC-EXTN-1004 - Unable to retrieve entity fields for "productprice" entity from OroCommerce.
Description: The integration could not read the Product Price entity structure from OroCommerce while preparing default pricing.
Resolution: Confirm the connected OroCommerce account is reachable and that the Product Price entity is available, then re-transfer. If it persists, your MiSP (managed integration service provider) can validate connectivity in a staging environment and, if they confirm an integration fault, raise it with iPaaS.com Support.
Duplicate SKU conflict
When a product is created and its SKU is already present in OroCommerce, OroCommerce reports a uniqueness conflict through the API. The integration surfaces that conflict as OROC-EXTN-1001 (see General and Identifier). How the integration responds depends on the Collision Handling Method set on the product mapping collection: with Error, the conflict is reported and nothing is created or updated; with Remap and Link, Update and Link, or Update and No Link, the integration matches the existing product by SKU and updates and/or links it instead of failing. To have duplicate SKUs update the existing product rather than fail, set the Collision Handling Method on the product mapping collection accordingly (the product collections ship with Update and Link). The methods are described in the OroCommerce Simple, Configurable, and Kit Product mapping documentation.
Product Variant
Variant option values required
OROC-VALD-1017 - Variant Option Values are not found for this variant "{sku}" sku. At least one is required to create variant product in OroCommerce.
Description: A product variant was sent with no variant option values, which OroCommerce requires to create a variant.
Resolution: Add at least one variant option value to the variant in iPaaS.com before re-transferring.
Variant attribute option required
OROC-VALD-1018 - Attribute option is required to create variant product. Product sku: {sku}
Description: A variant is missing the attribute option needed to create it in OroCommerce.
Resolution: Confirm the variant's attribute option value is mapped and present in iPaaS.com, then re-transfer.
Variant product Id required for update
OROC-VALD-1019 - Variant Product ID is required for Update.
Description: An update was attempted for a variant that has no resolved OroCommerce ID.
Resolution: Confirm the variant was created in OroCommerce first so its external ID is stored, or run the record through the create operation instead of update.
Variant product type must be simple
OROC-BIZL-1005 - Invalid product type '{type}'. ProductVariant from iPaaS can only be created in OroCommerce when product type is 'simple'.
Description: A product variant was sent with a product type other than simple. The update path reports the equivalent message ending "can only be updated in OroCommerce when product type is 'simple'."
Resolution: Set the variant's product type to simple in iPaaS.com and re-transfer.
Variant option not pre-defined in OroCommerce
OROC-NFND-1001 - Option "{option}" and Value "{value}" must be pre-defined in OroCommerce product attributes and assigned to the Product Family
Description: Raised by the variant options mapping collection's filter when a variant's option name or value does not already exist as an OroCommerce product attribute assigned to the product family. The variant options are skipped until the attribute exists.
Resolution: In OroCommerce, create the product attribute and its option value, assign it to the relevant product family, then re-transfer the variant.
Default pricing required values (variant)
OROC-VALD-1020 - Default pricing {value} is required for creating a product variant.
Description: One or more required default-pricing values were missing when the product variant was created or updated. The specific value is named in the message — one of: type, attribute value, attribute quantity, attribute currency, the relationship price list id/type, or the relationship unit id/type.
Resolution: Populate the missing default-pricing mappings for the variant so each required value resolves to a non-empty value, then re-transfer.
The Product Variant flow shares the Default Pricing custom field validation and the Product Price entity read with products — see OROC-BIZL-1003, OROC-BIZL-1004, and OROC-EXTN-1004 under Product for those messages and resolutions.
Bulk Pricing (Price List)
Price list name required
OROC-VALD-1005 - Price Lists Name is required
Description: The Price List name value did not resolve during the transfer.
Resolution: Confirm the Price List Name mapping produces a non-empty value before re-transferring.
Price list currency required
OROC-VALD-1006 - At least one Price Lists Currency is required
Description: The Price List was sent without any currency.
Resolution: Map at least one valid Price List currency and re-transfer.
Product price required values
OROC-VALD-1007 - Product Prices Quantity is required
Description: A Product Price line was missing its quantity. The related codes cover the other required values:
OROC-VALD-1008(currency),OROC-VALD-1009(value),OROC-VALD-1010(product Id), andOROC-VALD-1011(unit Id).Resolution: Populate the indicated value. The Product ID and Unit ID resolve from the related product or variant in OroCommerce, so confirm the referenced product or variant has been transferred and that its currency and unit mappings exist.
Customer group required on price list assignment
OROC-VALD-1012 - Customer Group is required
Description: A Price List customer group assignment was processed without a customer group value.
Resolution: Confirm the customer group (customer category) reference resolves on the Bulk Pricing record before re-transferring.
Prerequisite customer category could not be created
OROC-BIZL-1014 - Unable to create customer category in HandlePrerequisite. This will prevent the transfer of the bulk pricing.
Description: A customer category (customer group) the Price List assignment depends on could not be created first.
Resolution: Confirm the referenced customer category exists in OroCommerce or that auto-create of customer groups is enabled, resolve the underlying customer group error, then re-transfer.
Prerequisite product could not be created
OROC-BIZL-1015 - Unable to create product {sku} in HandlePrerequisite. This will prevent the transfer of the bulk Pricing.
Description: Auto-create was enabled, but the product the Price List depends on could not be created first, so the Bulk Pricing transfer was stopped.
Resolution: Investigate and resolve the underlying product error (it is logged separately), confirm the product transfers successfully on its own, then re-transfer the Bulk Pricing.
Prerequisite parent product could not be created
OROC-BIZL-1016 - Unable to create parent product of variant {sku} in HandlePrerequisite. This will prevent the transfer of the bulk Pricing.
Description: Auto-create was enabled, but a variant's parent product that the Price List depends on could not be created first, so the Bulk Pricing transfer was stopped.
Resolution: Resolve the underlying parent-product error (logged separately), confirm the parent product transfers on its own, then re-transfer the Bulk Pricing.
A duplicate Price List name is rejected by OroCommerce and surfaced as OROC-EXTN-1001; ensure Price List names are unique, or adjust the Bulk Pricing dynamic formula that generates the name so it produces a unique value.
Customer
Address country required
OROC-VALD-1001 - Country is required
Description: A customer address was sent without its country.
Resolution: Populate the Country field for the address in iPaaS.com before re-transferring.
Address city required
OROC-VALD-1002 - City is required
Description: A customer address was sent without its city.
Resolution: Populate the City field for the address in iPaaS.com before re-transferring.
Address street required
OROC-VALD-1003 - Street is required
Description: A customer address was sent without its street.
Resolution: Populate the Street field for the address in iPaaS.com before re-transferring.
Address postal code required
OROC-VALD-1004 - PostalCode is required
Description: A customer address was sent without its postal code.
Resolution: Populate the PostalCode field for the address in iPaaS.com before re-transferring.
Cannot link existing customer category by name
OROC-BIZL-1006 - Unable to dynamically link to existing OroCommerce Customer Category (Customer Group) using Name. This may result in duplicate Customer Group records.
Description: The integration could not confirm the external ID link to an existing customer group by name, which risks creating a duplicate.
Resolution: Verify the customer category exists in OroCommerce with the expected name and that its external ID mapping is stored in iPaaS.com, then re-transfer.
Cannot link existing company address by fields
OROC-BIZL-1007 - Unable to dynamically link to existing OroCommerce Customer Address (Company Address) using Address Fields i.e Country, Region, Street, City, Postal Code. This may result in duplicate Customer Address records.
Description: The integration could not match an existing company address by its address fields, which risks creating a duplicate address.
Resolution: Confirm the address fields (Country, Region, Street, City, Postal Code) match the existing OroCommerce address, and that the address external ID mapping is stored in iPaaS.com.
Cannot link existing company by name
OROC-BIZL-1008 - Unable to dynamically link to existing OroCommerce company using iPaaS name: {name}. This may result in duplicate company records.
Description: The integration could not confirm the external ID link to an existing company by name, which risks creating a duplicate.
Resolution: Confirm the company exists in OroCommerce with the expected name and that its external ID mapping is stored in iPaaS.com.
Prerequisite customer category could not be created
OROC-BIZL-1013 - Unable to create customer category in HandlePrerequisite. This will prevent the transfer of the company.
Description: A customer category the company depends on could not be created first.
Resolution: Resolve the underlying customer group error, confirm the category transfers, then re-transfer the company.
OroCommerce may also reject a customer create or update with a passed-through validation message (for example, a required field missing, or a country or region name that does not exist in OroCommerce). Those surface as OROC-EXTN-1001 — populate the required fields (Name for the customer; Street, City, PostalCode, and Country for addresses) and confirm country and region names match OroCommerce's records exactly.
Customer Group
Customer group update Id missing
OROC-VALD-1021 - Cannot update CustomerGroup : Id is missing.
Description: An update was attempted for a customer group that has no stored OroCommerce ID.
Resolution: The customer group must already be linked by its OroCommerce ID, saved as the external ID in iPaaS.com, before it can be updated. If it has not been linked, run the record through the create (Add) operation rather than update so the link is established.
Payment term not found
OROC-NFND-1002 - Payment term was not found in OroCommerce.
Description: The payment term name supplied for the customer group did not resolve to a payment term in OroCommerce, so the related ID could not be set.
Resolution: Confirm the payment term name matches an existing OroCommerce payment term exactly, then re-transfer.
The payment term, tax code, and organization lookups used when building a customer group resolve from OroCommerce by name. If a supplied name does not match an OroCommerce record, the related ID is not resolved and OroCommerce may then reject the create or update on a missing required field, surfaced as OROC-EXTN-1001. Confirm the payment term, tax code, and organization names match existing OroCommerce records exactly.
Customer User
Customer user update Id missing
OROC-VALD-1022 - Cannot update CustomerUser : Id is missing.
Description: An update was attempted for a customer user that has no stored OroCommerce ID.
Resolution: Confirm the OroCommerce customer user ID is saved as the external ID in iPaaS.com, or run the record through the create operation rather than update.
Cannot link existing customer user by email
OROC-BIZL-1009 - Unable to dynamically link to existing OroCommerce customer user using iPaaS Email: {email}. This may result in duplicate customer user records.
Description: The integration could not confirm the external ID link to an existing customer user by email, which risks creating a duplicate.
Resolution: Confirm the customer user exists in OroCommerce with the expected email and that its external ID mapping is stored in iPaaS.com.
Cannot link existing customer user address by fields
OROC-BIZL-1010 - Unable to dynamically link to existing OroCommerce Customer Address using Address Fields i.e Country, Region, Street, City, Postal Code. This may result in duplicate Customer Address records.
Description: The integration could not match an existing customer user address by its address fields, which risks a duplicate.
Resolution: Confirm the address fields match the existing OroCommerce address and that the address external ID mapping is stored in iPaaS.com.
Order
Cannot link existing transaction by Id
OROC-BIZL-1012 - Unable to dynamically link to existing OroCommerce transaction using Id. This may result in duplicate transaction records.
Description: The integration could not confirm the external ID link to an existing order, which risks creating a duplicate.
Resolution: Confirm the order's external ID mapping is stored correctly in iPaaS.com before re-transferring.
An order whose match field is not one the integration recognizes surfaces as OROC-BIZL-1002 (see Product). If OroCommerce returns a response without a usable order ID, it is surfaced as OROC-EXTN-1002 (see General and Identifier).
Invoice
Invoice missing valid customer name
OROC-VALD-1031 - Invoice can not be created because it does not have valid Customer Name
Description: The invoice's customer could not be resolved — the transaction's Company ID, Customer ID, and Email Address all failed to match an existing OroCommerce customer or customer user. Because the customer name is required, the invoice is not created. This check runs in the invoice's CustomerName mapping formula.
Resolution: Ensure the transaction carries a valid Company ID, Customer ID, or Email Address that maps to an existing OroCommerce customer or customer user before re-transferring.
Prerequisite customer user could not be created
OROC-BIZL-1018 - Unable to create customer user in OroCommerce. This will prevent the transfer of the Invoice.
Description: The invoice transfers its customer as a prerequisite, and the customer user could not be created in OroCommerce (for example, a required link on the Customer User mapping did not resolve), so the whole invoice transfer was stopped.
Resolution: Resolve the underlying customer user error, which is logged separately — most often the company the customer user links to must exist in OroCommerce — then re-transfer the invoice.
Prerequisite customer could not be created
OROC-BIZL-1019 - Unable to create customer in OroCommerce. This will prevent the transfer of the Invoice.
Description: The invoice transfers its customer (company) as a prerequisite, and the customer could not be created in OroCommerce, so the whole invoice transfer was stopped.
Resolution: Resolve the underlying customer error, which is logged separately, confirm the customer transfers on its own, then re-transfer the invoice.
Invoice update Id missing
OROC-VALD-1023 - Cannot update Invoice: Id is missing.
Description: An update was attempted for an invoice that has no stored OroCommerce ID.
Resolution: Confirm the OroCommerce invoice ID is saved as the external ID in iPaaS.com, or run the record through the create operation rather than update.
Invoice line item update Id missing
OROC-VALD-1024 - Cannot update Invoice Line Item: Id is missing.
Description: An update was attempted for an invoice line item that has no stored OroCommerce ID.
Resolution: Confirm the OroCommerce line item ID is saved as the external ID in iPaaS.com, or run the record through the create operation rather than update.
A duplicate invoice number is rejected by OroCommerce with an HTTP 409 conflict and surfaced as OROC-EXTN-1001 (for example, "Error calling OroCommerce CallWrapper.Invoice.POST: … conflict constraint … The entity already exists. (Http Code: Conflict)"). To have a re-processed invoice update the existing record rather than fail, set the Collision Handling Method on the invoice mapping collection to Remap and Link or Update and Link; otherwise ensure transaction numbers are unique. OroCommerce accepts only draft or posted for an invoice's internal status; the Status mapping translates the transaction status and defaults unrecognized values to draft, so an unmapped status does not by itself produce an error.
Shipping Tracking
Shipping tracking update Id missing
OROC-VALD-1025 - Cannot update ShippingTracking : Id is missing.
Description: An update was attempted for a shipping tracking record that has no stored OroCommerce ID.
Resolution: Confirm the OroCommerce shipping tracking ID is saved as the external ID in iPaaS.com, or run the record through the create operation rather than update.
Cannot link existing shipping tracking
OROC-BIZL-1011 - Unable to dynamically link to existing OroCommerce Shipping Tracking using Tracking Method, Tracking Number and Order Id. This may result in duplicate Shipping Tracking records.
Description: The integration could not match an existing shipping tracking record by its tracking method, tracking number, and order ID, which risks a duplicate.
Resolution: Confirm those values match the existing OroCommerce record and that the external ID mapping is stored in iPaaS.com.
Connection and Authentication
Refresh token revoked
OROC-AUTH-1001 - Refresh Token is revoked and The refresh token is invalid. Please re-authorize the subscription manually from subscription settings page
Description: The stored OAuth refresh token is no longer valid, so the integration cannot obtain a new access token.
Resolution: Re-authorize the OroCommerce subscription from the subscription settings page in iPaaS.com.
Access token exchange by authorization code failed
OROC-AUTH-1002 - OroCommerce Get Access Token Request By Authorization Code Failed while the exception message is: {message}
Description: OroCommerce rejected the request to exchange the authorization code for an access token; the underlying reason is included in the message.
Resolution: Retry the authorization from the subscription settings page; if it continues to fail, confirm the Client ID, Client Secret, and Redirect URL are correct and that the OroCommerce account permits OAuth access.
Access token refresh failed
OROC-AUTH-1003 - OroCommerce Get Access Token Request By Refresh Token Failed: {message}
Description: OroCommerce rejected the request to obtain a new access token using the stored refresh token; the underlying reason is included in the message.
Resolution: Re-authorize the OroCommerce subscription from the subscription settings page. If it continues to fail, confirm the OroCommerce account and its OAuth application are still active.
OAuth Client ID preset missing
OROC-AUTH-1004 - Unable to complete OAuth process in ProcessAuthorization. ClientId is not specified in the Subscription Settings Preset
Description: The Client ID required for OAuth is missing from the subscription settings.
Resolution: Enter the Client ID in the OroCommerce subscription settings and re-authorize.
OAuth Client Secret preset missing
OROC-AUTH-1005 - Unable to complete OAuth process in ProcessAuthorization. ClientSecret is not specified in the Subscription Settings Preset
Description: The Client Secret required for OAuth is missing from the subscription settings.
Resolution: Enter the Client Secret in the OroCommerce subscription settings and re-authorize.
OAuth Redirect URL preset missing
OROC-AUTH-1006 - Unable to complete OAuth process in ProcessAuthorization. RedirectUrl is not specified in the Subscription Settings Preset
Description: The Redirect URL required for OAuth is missing from the subscription settings.
Resolution: Enter the Redirect URL in the OroCommerce subscription settings and re-authorize.
OAuth code could not be exchanged for a token
OROC-AUTH-1007 - Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token
Description: The authorization code returned by OroCommerce could not be exchanged for an access token.
Resolution: Retry the authorization from the subscription settings page; if it continues to fail, confirm the Client ID, Client Secret, and Redirect URL are correct and that the OroCommerce account permits OAuth access.
Connection validation failed
OROC-AUTH-1008 - {OroCommerce connection validation message}
Description: The integration could not validate the connection to OroCommerce; the validation message returned by OroCommerce is surfaced in the log.
Resolution: Confirm the OroCommerce URL and credentials in the subscription settings are correct and that the OroCommerce instance is reachable, then re-authorize if needed.
General and Identifier
OroCommerce API call failed
OROC-EXTN-1001 - Error calling OroCommerce CallWrapper.{action}: {message} (Http Code: {code})
Description: A call to OroCommerce failed, and the integration surfaces the API's own error text along with the operation name and HTTP status code. This is the catch-all for OroCommerce rejecting a call — validation failures, rejected required fields (for example, "Required field is missing." or "Country or Region not found."), duplicate/conflict responses (HTTP 409), a customer group that has not been transferred ("Customer group not found."), and case-sensitive value mismatches (for example, a static Type value such as customers, customeraddresses, customergroups, pricelists, or customertaxcodes that does not match OroCommerce's expected casing).
Resolution: Read the passed-through message and HTTP status code, correct the reported field or value (including the exact casing of static Type values, and any missing required field), and re-transfer. For conflict (409) responses on a re-transfer, see the collision handling guidance in the Product and Invoice flows. If the failure is transient (for example, a timeout or a 5xx), re-transfer once the OroCommerce service recovers.
Unexpected response - Id not returned
OROC-EXTN-1002 - Unexpected response from OroCommerce API. Id was either not returned, or we were unable to extract it from the API response.
Description: A record (order, invoice, or invoice line item) was sent to OroCommerce but the response did not contain a usable ID, so the integration could not confirm the result.
Resolution: Check the OroCommerce error log entry recorded alongside this message for the underlying API response, correct any validation problem it reports, and re-transfer. If the response is consistently malformed after that, your MiSP can validate the behavior in a staging environment and, if they confirm an integration fault, raise it with iPaaS.com Support.
Batch run exception
OROC-EXTN-1003 - Recieved an exception during batch run on of {action}. {message}
Description: A grouped batch of OroCommerce calls failed, and the first underlying error is included in the message.
Resolution: Read the included underlying message to identify the failing record or field, correct it, and re-transfer. If the underlying error is itself one of the codes in this article, follow that code's resolution.
Primary ID empty
OROC-VALD-1026 - Primary ID cannot be empty
Description: An operation was attempted for a record whose primary ID was empty.
Resolution: Confirm the record's identifier or external ID is populated before transferring.
Invalid key value (integer expected)
OROC-VALD-1027 - Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = Integer, PKValue = {value}
Description: A record's identifier was expected to be a plain integer but the supplied value was not.
Resolution: Confirm the identifier (or external ID mapping) for the affected record is a valid integer, with no extra separators or text.
Invalid key value (one separator expected)
OROC-VALD-1028 - Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = String with one separator, PKValue = {value}
Description: A composite identifier was expected to contain exactly one separator but did not.
Resolution: Confirm the external ID for the affected record follows the documented two-part composite format (for example, a child ID joined to its parent ID by a single separator).
Invalid key value (two separators expected)
OROC-VALD-1029 - Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = String with two separator, PKValue = {value}
Description: A composite identifier was expected to contain exactly two separators but did not.
Resolution: Confirm the external ID for the affected record follows the documented three-part composite format described for that collection.
Invalid primary key data
OROC-VALD-1030 - Invalid data passed to {entity}.SetPrimaryKey: {value}
Description: The integration could not parse a primary key value supplied for a record.
Resolution: Confirm the identifier or external ID for the affected record is in the expected format for that collection, then re-transfer.