A custom field error means a custom field referenced in your request is invalid, does not exist, or does not match the expected configuration.
Every error in this family includes a stable code (for example VALD-1011). Find that code in the table at the bottom of this article to see exactly which rule was triggered.
Common causes
The custom field does not exist.
The custom field name or key is misspelled.
The value does not match the custom field type.
How to fix it
Match the code in your response to the table below.
Confirm the custom field exists in your configuration.
Check the field name and that the value matches its type.
Re-send the request.
Codes in this family
Code | What it means |
| {customFieldName} custom field does not exist or can not be found. |
| Only Template Custom Fields can be used with Template Mappings. Please create the template custom field and try again. |
| Only Template Custom Fields are allowed with Template Mappings. Source Table: {sourceTable} |
| Only Template Custom Fields are allowed with Template Translation Collections. Source Table: {sourceTable} |
| Invalid {sourceOrDestination} template custom field id: {fieldId}. |
| You can only use template-defined custom fields in template mappings. |
Related
Custom Fields
Mapping data between systems