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."],[[["`ImageError` objects detail issues encountered with images in Google Ad Manager."],["Errors can range from format and size issues to policy violations regarding animation, color, and Flash content."],["The `reason` field categorizes the specific image error using the `ImageError.Reason` enumeration."],["Density-related errors can arise with primary assets in high-density creatives."],["This documentation outlines the namespace and a table with inherited and specific `ImageError` fields."]]],["This document details the structure and potential errors within the Ad Manager API, specifically focusing on image-related issues. It lists various services like CreativeService and ForecastService, and outlines an inheritance structure for `ApiError`. A detailed list of `ImageError` reasons is provided, including issues like `INVALID_IMAGE`, `INVALID_SIZE`, and `FILE_TOO_LARGE`. It defines image errors such as format and size validity, animation restrictions, flash file restrictions, and general system failures.\n"]]