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-05-15 UTC."],[[["TechnologyTargetingError objects represent validation errors specific to technology targeting in Google Ad Manager."],["These errors can occur when attempting to target web technologies in mobile line items, or mobile technologies in web line items."],["The error might also indicate that specific features like mobile carrier targeting or device capability targeting are not enabled."],["Each TechnologyTargetingError includes a reason field that provides more details about the specific issue encountered."],["These errors are part of the Google Ad Manager API and are encountered when using services like ForecastService, LineItemService, and others."]]],["The content outlines various services and error types within an API, focusing on advertising management. Key services include AdjustmentService, ForecastService, LineItemService, and others. The document details error handling through `ApiError` and its many subtypes. `TechnologyTargetingError` is highlighted, along with the different errors it can be for, such as mobile/web targeting conflicts and feature inabilities like device targeting and carrier targeting. Each error has a string representation, and fields that describe where and what caused the error.\n"]]
