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."],[],["The content details the `CreativeService` and its associated error types within the ad manager API (v202411). It outlines `CreativeSetService` and `LineItemCreativeAssociationService` as related services, highlighting inheritance from `ApiError`. A comprehensive list of specific errors (e.g., `AssetError`, `AuthenticationError`) and their links are provided. Additionally, the document describes `SwiffyConversionError`, which handles errors during Flash to Swiffy conversion, listing specific reasons like `SERVER_ERROR` and `INVALID_FLASH_FILE`. Lastly, the document define the field of the errors.\n"]]
