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-11-19 UTC."],[[["CustomCreativeError objects detail issues encountered when working with custom creatives in Google Ad Manager."],["These errors can arise from various sources, including duplicate macro names, referencing missing macros, or using unsupported macros."],["The 'reason' field within the error object provides a specific code indicating the nature of the problem, such as 'DUPLICATE_MACRO_NAME_FOR_CREATIVE' or 'SNIPPET_REFERENCES_MISSING_MACRO'."],["Developers can use these error messages to identify and resolve issues related to custom creative implementation in their ad campaigns."]]],["The provided content outlines error handling within the `CreativeService`, focusing on `CustomCreativeError` and its potential `Reasons`. Key error types include issues with API versions, authentication, collections, assets, creatives, templates, and custom fields. Specific `CustomCreativeError` reasons include duplicate macro names, missing or unrecognized macros, disallowed custom creatives, and duplicate assets in macros. The `ApiError` class, inherited, specifies details like field path, trigger, and error string. Information about `CreativeSetService` and `LineItemCreativeAssociationService` are also listed.\n"]]
