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 details various services within an ad management system, including AdRule, Adjustment, AdsTxt, AudienceSegment, and many others totaling over 40. These services manage aspects like content, creatives, forecasting, inventory, line items, and targeting. It also outlines an inheritance structure for errors stemming from `ApiError`, such as `RequiredError`, which signals missing fields. The error system provides specific reasons, `fieldPath`, `trigger`, and `errorString` for troubleshooting, with `REQUIRED` indicating a missing field.\n"]]
