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."],[[["\u003cp\u003eThe \u003ccode\u003ePrecisionError\u003c/code\u003e object is part of the Google Ad Manager API and falls under the \u003ccode\u003eLineItemTemplateService\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eIt is used to indicate issues with the precision of numerical values, specifically when they do not adhere to the required format.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003ePrecisionError\u003c/code\u003e inherits from \u003ccode\u003eApiError\u003c/code\u003e, providing additional context about the error.\u003c/p\u003e\n"],["\u003cp\u003eTwo primary reasons for \u003ccode\u003ePrecisionError\u003c/code\u003e are: \u003ccode\u003eWRONG_PRECISION\u003c/code\u003e (incorrect decimal places) and \u003ccode\u003eUNKNOWN\u003c/code\u003e (unspecified reason).\u003c/p\u003e\n"],["\u003cp\u003eDevelopers using the API should refer to this documentation to handle \u003ccode\u003ePrecisionError\u003c/code\u003e and ensure data accuracy.\u003c/p\u003e\n"]]],["The provided content details several services like `ForecastService`, `LineItemService`, `LineItemTemplateService`, `NetworkService`, `OrderService`, `ProposalLineItemService`, and `ProposalService`. It also outlines error inheritance under `ApiError`, including numerous specific error types. `PrecisionError` is identified with the reasons `WRONG_PRECISION`, indicating incorrect numerical precision, and `UNKNOWN`, representing an undefined reason. The Field `fieldPath` shows the OGNL field path where the error was found.\nErrors associated with number precisions are limited to the `PrecisionError` type, specifically when the `reason` field is set to `WRONG_PRECISION`. This indicates that a number's least significant digits were not zero as required.\n"],null,[]]