A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-20 UTC."],[[["`CustomFieldValueError` occurs when there are issues with custom field values during editing."],["This error can be triggered by various reasons, including a missing custom field, an inactive custom field, or an invalid entity type."],["The error provides details such as the field path, trigger data, and a specific reason code for easier debugging."],["`CustomFieldValueError` is part of a broader error hierarchy inherited from `ApiError`, which includes other common API errors."],["Developers can use the provided reason codes and error details to identify and resolve the issue causing the `CustomFieldValueError`."]]],["The content details the `CustomFieldValueError` within the context of various services like `CompanyService`, `CreativeService`, and others. It outlines error management related to custom field values, including reasons like `CUSTOM_FIELD_NOT_FOUND`, `CUSTOM_FIELD_INACTIVE`, and `INVALID_ENTITY_TYPE`. The structure includes `ApiError` inheritance and specific error fields such as `fieldPath`, `trigger`, and `reason`. It defines how `CustomFieldValue` modifications or creations are validated and the types of errors that can occur.\n"]]
