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 document outlines various services, including AdRuleService, CompanyService, and others, within an API framework. It details the inheritance structure of `ApiError`, which is the parent for numerous specific error types like `AdRuleError` and `AuthenticationError`. The `RequiredNumberError` is used for validation, indicating issues like `TOO_LARGE` or `TOO_SMALL` values and is used for number validators. Key fields are `fieldPath`, `trigger`, `errorString` and `reason`, along with enumerations for different error reasons.\n"]]