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 content outlines the structure and potential errors for operating on line items within an ad management system. Key services include Forecast, LineItem, LineItemTemplate, Order, ProposalLineItem, Proposal, and PublisherQueryLanguage. Errors, derived from `ApiError`, are categorized, including `LineItemOperationError`. This error type specifies reasons like \"NOT_ALLOWED,\" \"HAS_COMPLETED,\" or \"CANNOT_ACTIVATE_LEGACY_DFP_LINE_ITEM\", detailing issues that prevent actions on line items, such as insufficient permissions, completed status, or the line item type. It define error field like \"fieldPath\", \"fieldPathElements\", \"trigger\", \"errorString\" and \"reason\".\n"],null,[]]