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."],[[["ProposalLineItemService manages proposal line items and their associated errors in Google Ad Manager."],["It inherits from ApiError and introduces a specific TeamError for team-related issues."],["TeamError provides reasons for errors related to entities, ad units, placements, and team assignments."],["Errors can indicate issues with user access, entity visibility within teams, or team status."],["Developers can use these error codes to understand and address issues with proposal line items and teams."]]],["The content details services and error types within an API, focusing on `ProposalLineItemService`. It lists numerous service endpoints like `CompanyService`, `ForecastService`, and `OrderService`. A wide array of errors inherit from `ApiError`, including `AuthenticationError`, `QuotaError`, and `TeamError`. `TeamError` specifics are provided, with reasons like `ENTITY_NOT_ON_USERS_TEAMS` and `CANNOT_UPDATE_INACTIVE_TEAM`. The `ApiError` class contains fields such as `fieldPath`, `trigger`, and `errorString` to explain the error.\n"]]