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-02-20 UTC."],[],["The document details errors for line item operations in ad management services, including `ForecastService`, `LineItemService`, and `OrderService`. It lists various error types like `ApiError`, `ForecastError`, and `LineItemError`, alongside specific error reasons such as `NOT_ALLOWED`, `HAS_COMPLETED`, and `CANNOT_ACTIVATE_UNCONFIGURED_LINE_ITEM`. The document explains `LineItemOperationError` and its properties such as reason and the field path for identifying the error cause. It includes fields like field path, error string, trigger, and reason.\n"]]