Overview
This article lists the error messages the Pimcore integration can record in the iPaaS.com error logs during a transfer, what causes each one, and how to resolve it. Each error carries a stable code (for example PIMC-BIZL-1001) shown at the start of the message — search this page for that code to jump straight to its entry. Errors appear in iPaaS.com under Dashboard → Integration Monitoring → Error Logs. For non-error behaviors (records skipped because a reference does not yet exist, required-field expectations, and other design behaviors), see the Pimcore Integration Known Limitations and the Pimcore mapping documentation.
Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who manages your integration's mappings, configuration, and credentials. If a resolution is beyond what you can adjust yourself, your MiSP is the first point of contact.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Configuration
Product and Variant Transfers
Category Assignments
Error Collection
Configuration
Unrecognized Class Name
PIMC-BIZL-1001 - The class name prefixed to the id ([class name]) does not exist in the list of available class names. [list of configured class names]
Description: A record received from Pimcore belongs to a class that is not listed in the matching Class Names subscription setting, so the integration cannot build the external id that links the record in iPaaS.com.
Resolution: Add the record's Pimcore class to the appropriate Class Names setting — for example Product Class Names, Product Category Class Names, or Variant Class Names — on the subscription settings page, then re-run the transfer. See Pimcore Connections and Settings.
Product and Variant Transfers
Object Has No Custom Fields
PIMC-BIZL-1002 - The object supplied does not have readable custom fields
Description: A mapping formula attempted to read custom field values from an object that has no custom fields available.
Resolution: Confirm the custom fields used by the formula are defined in the subscription and that the formula references the correct object. This is a Dynamic Formula error and can be corrected by editing the mapping in the mapping editor.
Variant Option Field Has No Custom Field
PIMC-BIZL-1003 - ParseVariantOptionValuesFromFields: Attempt to use [field name] as an option field, but there is no custom field entry for it
Description: A variant-option formula names a field as an option field, but no custom field is defined for that field path, so its value cannot be read.
Resolution: Define a custom field for the named field path, or correct the field name in the formula. This is a Dynamic Formula error and can be corrected in the mapping editor.
Pimcore API Call Failure
PIMC-EXTN-1001 - Error calling Pimcore CallWrapper.[action] [Pimcore error detail]
Description: The integration called the Pimcore Datahub GraphQL API and Pimcore returned an error, or the call could not be completed. The logged message includes the action being performed and the specific error text returned by Pimcore.
Resolution: Read the Pimcore error detail included in the message. Common causes are a Datahub GraphQL endpoint or API key that is misconfigured, or a class or field that is not exposed in the Datahub configuration. Confirm the API Url, API Key, and Datahub Config values on the subscription settings page and that the Pimcore Datahub endpoint is reachable, then re-run the transfer. See Pimcore Connections and Settings. If the Pimcore error persists after the connection is confirmed, contact your MiSP.
Unexpected Pimcore Response
PIMC-EXTN-1002 - Invalid JSON data: missing 'get[ClassName]' node.
Description: The integration requested a record from Pimcore, but the response did not contain the expected data node for the class. This usually means the class or its query is not exposed as expected in the Pimcore Datahub GraphQL configuration.
Resolution: In Pimcore, confirm the Datahub GraphQL configuration exposes the class named in the message (its query and fields), and that the class name matches the configured Class Names setting. See the Pimcore Installation Instructions and Pimcore Connections and Settings, then re-run the transfer.
Category Assignments
Category Assignment Transferred Directly
PIMC-BIZL-1004 - Product Category Assignments are not supported as primary transfer requests
Description: A product category assignment was requested as a primary transfer — for example, a Manual Sync of an assignment on its own. Category assignments transfer only as part of the product or variant they belong to.
Resolution: Transfer the product or variant instead; its category assignments transfer with it.