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 2025-08-06 UTC."],[],["The document details errors encountered during line item operations within ad management services. Core services include Forecast, LineItem, LineItemTemplate, Order, Proposal, and PublisherQueryLanguage. Errors, inheriting from `ApiError`, contain fields like `fieldPath`, `trigger`, and `errorString`. `LineItemOperationError` specifies reasons for operation failures, including `NOT_ALLOWED`, `NOT_APPLICABLE`, `HAS_COMPLETED`, `CANNOT_ACTIVATE_UNCONFIGURED_LINE_ITEM`, and `CANNOT_DELETE_DELIVERED_LINE_ITEM`. The `reason` field uses an enumeration to define specific causes.\n"],null,[]]