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-08-20 UTC."],[[["BillingError objects list errors related to billing settings for proposals and proposal line items."],["These errors can be caused by unsupported billing schedules, caps, or missing billing sources."],["Billing settings might have restrictions depending on the proposal type (e.g., offline)."],["Once a proposal is approved, billing settings usually cannot be updated."],["The `reason` field provides a specific code indicating the nature of the billing error."]]],["The `ProposalLineItemService` manages proposal line items and inherits from `ApiError`. It lists various error types, including `BillingError`. This service handles issues like `AuthenticationError`, `ForecastError`, `ProposalError`, etc. `BillingError` specifies problems with billing schedules, caps, and sources. Error reasons include unsupported settings, missing billing information, invalid sources for offline proposals, and the inability to update billing after proposal approval. The service's namespace is defined, along with field details.\n"]]
