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."],[],["This document outlines the errors associated with executing operations on line items within the ad management system. Key services include ForecastService, LineItemService, LineItemTemplateService, OrderService, ProposalLineItemService, ProposalService, and PublisherQueryLanguageService. It details the `LineItemOperationError` class, which inherits from `ApiError` and lists various error reasons, such as `NOT_ALLOWED`, `NOT_APPLICABLE`, `HAS_COMPLETED`, `HAS_NO_ACTIVE_CREATIVES`, and credit status errors. It defines a variety of field paths, triggers, error strings, and enumerations within the `LineItemOperationError`.\n"],null,[]]