Overview
This article lists the error messages the Pimcore integration can produce during a transfer, what causes each one, and how to resolve it. 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.
Supported Flows
Configuration
Product and Variant Transfers
Category Assignments
Configuration
Unrecognized Class Name
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
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
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.
Category Assignments
Category Assignment Transferred Directly
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.