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-08-20 UTC."],[[["`DealError` objects represent errors encountered when creating or updating programmatic proposals."],["These errors often occur due to issues like missing proposal line items, a proposal being sold, or required buyer approval."],["`DealError` details include a reason code (e.g., `CANNOT_ADD_LINE_ITEM_WHEN_SOLD`) and standard error fields like `fieldPath`."],["Programmatic proposals require specific considerations, such as an environment and association with an Ad Exchange property."],["The `DealError.Reason` enumeration provides a comprehensive list of potential error scenarios."]]],["The document details error handling within the Ad Manager API, specifically for `DealError` and related services. `DealError` addresses issues in proposal management, including actions like adding, archiving, and modifying proposal line items, and handling proposals that are already sold. It also covers proposal synchronization with the marketplace and conditions requiring buyer approval. The errors inherit properties from `ApiError`, such as `fieldPath`, and `errorString`. There are specific error types listed within the `PublisherQueryLanguageService`.\n"]]
