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 a variety of services within an ad management platform, including AdRule, Adjustment, AdsTxt, AudienceSegment, and many others, each identified by a unique service name. These services cover areas like content, creatives, forecasting, inventory, and reporting. It also details a hierarchical structure of API errors, derived from a base `ApiError`, with specific error types like `RequiredError`, indicating missing fields, along with various other specialized errors, such as `AuthenticationError`, and `QuotaError`. The `RequiredError` contains a reason, and an enum of \"Required\" to denote a missing field.\n"]]
