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."],[],["The core content details various services and their associated errors within a specific API version (v202411). Key services include ForecastService, LineItemService, LineItemTemplateService, NetworkService, OrderService, ProposalLineItemService, and ProposalService. A significant portion lists errors like ApiError, AssetError, and numerous others. The `PrecisionError` is highlighted as it is an inherited error and its associated `reason` can be `WRONG_PRECISION`, or `UNKNOWN`. The error specifies wrong number of digits.\n\nThe errors related to precisions are:\n* **PrecisionError**: Specifies that the number has a wrong precision.\n* `PrecisionError.Reason`: Specifies the reason of `PrecisionError`. It can be `WRONG_PRECISION` or `UNKNOWN`\n"]]