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-02-13 UTC."],[[["OrderActionError objects encompass all errors encountered when executing actions on Order objects within the system."],["These errors stem from various sources, including permission issues, order status conflicts (archived, ended, unreserved line items), company credit status, and delivered line items."],["OrderActionError objects inherit from ApiError, providing a structured way to identify the cause, trigger, and a textual representation of the error."],["Developers can leverage the `reason` field within OrderActionError objects to understand the specific nature of the error and take appropriate corrective measures."]]],["The content outlines error handling for ad management services, specifically focusing on `OrderActionError`. It details the `OrderActionError` as an extension of `ApiError` and lists its properties: `fieldPath`, `fieldPathElements`, `trigger`, and `errorString`. Additionally, it provides `OrderActionError` reasons, including `PERMISSION_DENIED`, `NOT_APPLICABLE`, `IS_ARCHIVED`, `HAS_ENDED`, `CANNOT_APPROVE_WITH_UNRESERVED_LINE_ITEMS`, `CANNOT_DELETE_ORDER_WITH_DELIVERED_LINEITEMS`, `CANNOT_APPROVE_COMPANY_CREDIT_STATUS_NOT_ACTIVE` and `UNKNOWN`, explaining when each error reason occurs.\n"]]
