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-11-19 UTC."],[[["The ForecastService API provides methods for forecasting potential ad delivery and revenue."],["It returns specific errors, represented by the `TeamError` type, when issues occur related to Teams."],["`TeamError` details reasons like invalid team assignments or entities not being on user's teams."],["These errors help developers debug and handle situations involving team access and permissions within the ad system."],["Refer to the provided table for the hierarchy of error types and their corresponding details for effective troubleshooting."]]],["The content details services and error types within an API, focusing on `ForecastService` and `TeamError`. It outlines various services like `CompanyService`, `ContactService`, `InventoryService`, among others. `ForecastService` lists numerous error types inherited from `ApiError`, including `AuthenticationError`, `QuotaError`, and `StringLengthError`. `TeamError` specifies reasons such as `ENTITY_NOT_ON_USERS_TEAMS` and `CANNOT_UPDATE_INACTIVE_TEAM`, defining team-related access and modification constraints. Fields for `ApiError` include `fieldPath`, `trigger`, and `errorString`.\n"]]