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 services including CompanyService, ContactService, NetworkService, OrderService, PublisherQueryLanguageService, and UserService. It outlines the inheritance of ApiError, with numerous specific error types such as ApiVersionError, AssetError, and many others related to various aspects like targeting, creatives, and quotas. InvalidEmailError is highlighted as a distinct error, occurring when an email attribute value is not a valid email address, with reasons like INVALID_FORMAT and UNKNOWN. Field information for ApiError and InvalidEmailError is presented.\n"]]
