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 2024-05-15 UTC."],[[["This page lists all the errors specifically related to custom creatives within the Google Ad Manager API."],["`CustomCreativeError` objects contain a `reason` field, which provides detailed information about the specific error encountered, categorized using the `CustomCreativeError.Reason` enum."],["The `reason` field helps identify issues like duplicate macro names, missing macros, unrecognized macros, and more, offering guidance on troubleshooting custom creative errors."],["The provided table outlines the structure of `CustomCreativeError` and its inherited properties from `ApiError`, along with their descriptions and data types."],["Developers can use this information to understand and handle custom creative errors effectively when working with the Google Ad Manager API."]]],["The document details error types for services like `CreativeService` and `CreativeSetService`, focusing on `LineItemCreativeAssociation`. It lists numerous `ApiError` subtypes, including `CustomCreativeError`, which is core to this context. `CustomCreativeError` specifies reasons like `DUPLICATE_MACRO_NAME_FOR_CREATIVE` and `UNRECOGNIZED_MACRO` for issues. Other errors encompass authentication, file, URL, and format errors, alongside limits and missing elements. Each error has fields such as `fieldPath`, `trigger`, and `errorString` for detailed diagnostics.\n"]]
