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."],[[["The `TeamError` object in Google Ad Manager's API represents errors related to team access and management."],["It provides information about why a team-related operation failed, such as invalid team assignments or missing team associations."],["The `reason` field within `TeamError` gives a specific reason for the error, like entities not being on a user's teams or incorrect ad unit associations with order teams."],["Developers can use this information to troubleshoot and resolve issues with team-based workflows in their Ad Manager integrations."]]],["The content details services and their associated errors within an API. Key services include Company, Forecast, Inventory, LineItem, and others. The document outlines the inheritance of `ApiError`, listing numerous specific error types such as `AdSenseAccountError`, `AuthenticationError`, and `InternalApiError`. `TeamError` is specifically defined with reasons like `ENTITY_NOT_ON_USERS_TEAMS`, `MISSING_USERS_TEAM`, and `CANNOT_UPDATE_INACTIVE_TEAM`, detailing conditions for team-related issues. Additionally it details `fieldPath`, `fieldPathElements`, `trigger` and `errorString`.\n"]]