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 services and errors within an ad management API. It lists numerous services like AdRule, AdsTxt, AudienceSegment, and CreativeService, among others, each with associated error types (e.g., StringFormatError). The StringFormatError details reasons for invalid string inputs, such as illegal characters or an invalid format. It includes error details, like the field path causing the issue. It defines the namespace, and lists several error codes related to input string formating, such as, ILLEGAL_CHARS and INVALID_FORMAT.\n"]]
