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-11-19 UTC."],[[["CustomFieldValueError occurs when there are issues with custom field values during editing."],["It might be triggered due to reasons like the custom field not existing, being inactive, or having an invalid entity type."],["This error is applicable to various services such as CompanyService, CreativeService, and LineItemService, among others."],["The error includes details like field path, trigger data, and a specific reason code for easier debugging."],["It inherits from ApiError, providing a general framework for handling API-related errors."]]],["The document details `CustomFieldValueError`, an error type within the ad manager API, specifically version 202411. This error arises when modifying custom field values across multiple services like Company, Creative, Forecast, LineItem, and others. `CustomFieldValueError` outlines reasons for failure, including non-existent or inactive custom fields/options, wrong entity type association, with specific reasons such as `CUSTOM_FIELD_NOT_FOUND`, `CUSTOM_FIELD_INACTIVE`, `CUSTOM_FIELD_OPTION_NOT_FOUND`, `INVALID_ENTITY_TYPE` and `UNKNOWN`. It inherits from `ApiError`, with additional fields for error identification.\n"]]
