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 encompass issues related to billing settings within proposals and proposal line items."],["These errors provide structured details including an error reason, a field path indicating the location of the error, and potential trigger data."],["Common BillingError reasons include unsupported billing schedules or caps, missing billing information, and invalid billing sources."],["Billing settings for proposals cannot be updated post-approval, potentially resulting in BillingError if modification is attempted."],["Developers can use the BillingError details, such as reason and field path, to diagnose and address billing-related issues within their applications."]]],["The `ProposalService` and `ProposalLineItemService` handle billing, encountering errors like unsupported schedules/caps, missing billing sources/schedules/caps, and invalid billing sources. `BillingError` inherits from `ApiError`, providing details such as field path, trigger, and a string representation. The `BillingError` enum specifies the error reasons, including missing or invalid billing components and disallowed updates. It also handles general API issues through error types such as permission errors and quotas errors.\n"]]
