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."],[[["\u003cp\u003eThe provided documentation details the \u003ccode\u003eStringFormatError\u003c/code\u003e in Google Ad Manager's API, which indicates issues with the format or content of input strings.\u003c/p\u003e\n"],["\u003cp\u003eIt lists various services and inheritance structures related to the error, offering context for its occurrence.\u003c/p\u003e\n"],["\u003cp\u003eThe error includes fields like \u003ccode\u003efieldPath\u003c/code\u003e, \u003ccode\u003etrigger\u003c/code\u003e, and \u003ccode\u003eerrorString\u003c/code\u003e for identifying the cause and location of the issue.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ereason\u003c/code\u003e field further clarifies the error, with potential values such as \u003ccode\u003eILLEGAL_CHARS\u003c/code\u003e or \u003ccode\u003eINVALID_FORMAT\u003c/code\u003e to pinpoint the specific problem.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can use this information to troubleshoot and resolve string formatting errors encountered while interacting with the Ad Manager API.\u003c/p\u003e\n"]]],["This content details various services and errors within an ad management system. Services include managing ads, audiences, content, creatives, forecasts, inventory, and targeting. Error handling is categorized under `ApiError`, with specific errors like `StringFormatError` which arise from invalid string inputs. `StringFormatError` indicates issues like `ILLEGAL_CHARS` or `INVALID_FORMAT` and it contains `fieldPath`, `fieldPathElements`, `trigger`, `errorString` to help identify the invalid string.\n"],null,[]]
