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."],[[["BillingError objects highlight errors in billing settings for proposals or proposal line items."],["Errors can arise from unsupported schedules, caps, missing sources, or invalid settings."],["Detailed error reasons are categorized using the `BillingError.Reason` enumeration."],["The `fieldPath` and `trigger` properties offer insight into the error's origin."],["This information is crucial for troubleshooting and resolving billing-related issues in proposals."]]],["The core content outlines the `ProposalLineItemService` and its associated errors, inherited from `ApiError`. These errors cover a wide range of potential issues, including authentication, targeting, currency, and various proposal-specific problems like line item, action, and programmatic errors. `BillingError` specifically includes reasons such as unsupported billing schedules or caps, missing billing sources, and invalid billing bases. There are multiple errors that inherit from `ApiError`. The `BillingError` enumeration provides detailed error reasons.\n"]]
