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 and associated errors within an ad management system. Core services include managing ad rules, adjustments, audiences, content, creatives, forecasting, inventory, and reporting. Error handling is a key aspect, with `StringFormatError` being highlighted for issues like illegal characters or invalid formats in input strings. It describes the structure of the errors with fields like `fieldPath`, `trigger`, `errorString`, and specific reasons like `ILLEGAL_CHARS` or `INVALID_FORMAT`.\n"]]
