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-08-20 UTC."],[[["AssetError objects highlight issues encountered when working with assets within the system."],["These errors can arise from problems like non-unique asset names, file size or name exceeding limits, or missing essential information in dynamic allocation code."],["The `reason` field categorizes the specific cause of the error using an enum, providing details for troubleshooting and resolution."],["AssetError inherits from ApiError, providing a broader context of the error within the API interaction."]]],["The provided content outlines various services and errors related to asset management within an ad management system. Services include CreativeSet, Forecast, LineItemCreativeAssociation, LineItem, LineItemTemplate, and Order services. A key aspect is the \"AssetError,\" which inherits from \"ApiError,\" and lists reasons such as `NON_UNIQUE_NAME`, `FILE_NAME_TOO_LONG`, `FILE_SIZE_TOO_LARGE`, and `INVALID_ASSET_ID`. The document also defines how the errors are represented including `fieldPath`, `trigger`, `errorString`, and `reason`.\n"]]