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."],[],["This document outlines various services and associated errors within an ad management system, version v202502. It details services like AdRule, Adjustment, AdsTxt, AudienceSegment, and OrderService, among many others, alongside a comprehensive list of potential errors. These errors, like ApiError, StringFormatError, and numerous others. The `StringFormatError` specifically addresses issues such as illegal characters and invalid formats in input strings, listing `UNKNOWN`, `ILLEGAL_CHARS` and `INVALID_FORMAT` as the possible `reason`.\n"]]
