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."],[[["The ForecastService in Google Ad Manager is used to predict future inventory availability and potential revenue."],["CustomFieldValueError occurs when there are issues related to custom field values during forecasting operations."],["This error can be triggered by various reasons, such as an invalid custom field, inactive custom field, or incorrect entity type association."],["Developers can use the provided error details, including reason and field path, to troubleshoot and resolve the issue."],["Refer to the documentation for detailed descriptions of each CustomFieldValueError reason and their corresponding solutions."]]],["The content details various services like CompanyService, CreativeService, ForecastService, and others, all associated with a specific API version (v202408). It outlines the `CustomFieldValueError`, which covers errors when manipulating custom field values. Key error reasons include `CUSTOM_FIELD_NOT_FOUND`, `CUSTOM_FIELD_INACTIVE`, `CUSTOM_FIELD_OPTION_NOT_FOUND`, `INVALID_ENTITY_TYPE`, and `UNKNOWN`. Additionally, `ApiError`'s fields, `fieldPath`, `fieldPathElements`, `trigger`, and `errorString`, are explained. `CustomFieldValueError` has a field `reason` that is an enumeration.\n"]]
