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-02-13 UTC."],[[["The `LineItemTemplateService.AssetError` object lists all errors associated with assets in Google Ad Manager."],["It inherits from `ApiError` and includes an additional `reason` field, which provides specific details about the asset error."],["The `reason` field can be one of several enumerations, such as `NON_UNIQUE_NAME`, `FILE_SIZE_TOO_LARGE`, and `INVALID_ASSET_ID`, indicating the nature of the error."],["This error is commonly encountered when working with services like `CreativeService`, `CreativeSetService`, and others listed in the provided content."],["Developers can utilize the error information, specifically the `reason` field, to troubleshoot and resolve issues related to assets within their Ad Manager integrations."]]],["The content details errors associated with various services in an ad management API, including `CreativeService`, `CreativeSetService`, `ForecastService`, `LineItemCreativeAssociationService`, `LineItemService`, `LineItemTemplateService`, and `OrderService`. It defines `ApiError` and `AssetError` as core error types. `AssetError` specifies reasons for asset-related issues such as `NON_UNIQUE_NAME`, `FILE_SIZE_TOO_LARGE`, or missing required parameters in code snippets. The error types also include `fieldPath`, `trigger`, `errorString`, and an error reason as core content.\n"]]