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."],[[["AssetError objects encompass a range of errors related to digital assets within the system."],["These errors can involve issues like non-unique asset names, excessive file size or length, and missing required parameters in dynamic allocation code."],["AssetError details include an error reason (represented by the 'reason' field), a field path indicating the location of the error, and a human-readable error message."],["It inherits from ApiError, providing additional context about the error such as field path and trigger data."]]],["The content details services and errors related to digital advertising assets. Services include CreativeSet, Forecast, LineItemCreativeAssociation, LineItem, LineItemTemplate, and Order services. Errors, all under `ApiError`, include specific `AssetError` categories like `NON_UNIQUE_NAME`, `FILE_NAME_TOO_LONG`, `INVALID_ASSET_ID`, and more related to asset file issues, code snippets, and naming. The namespace for these definitions is provided. Each error contains data such as a `fieldPath`, `trigger` and `errorString`, indicating the location, cause, and description of the error.\n"]]