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-05-15 UTC."],[[["This page lists all the errors that can occur when executing operations on line items."],["These errors encompass scenarios related to permissions, line item states, creative statuses, and company credit, among other factors."],["Each error is categorized by a specific reason, providing insight into the underlying issue."],["The errors are further detailed with explanations of the potential causes and implications."],["The documentation includes links to relevant resources for more context and troubleshooting."]]],["This document details error handling within an ad management API, specifically for line item operations. It lists several services like `ForecastService`, `LineItemService`, and `OrderService`, which are related to line item management. The `LineItemOperationError` is the core focus, presenting various reasons for errors. These reasons include `NOT_ALLOWED`, `NOT_APPLICABLE`, `HAS_COMPLETED`, and conditions related to creative status, company credit status, and deletion rules, along with an `UNKNOWN` catch-all. `ApiError` field contains metadata, including the `fieldPath`, `trigger`, and `errorString`.\n"]]
