type ProposalActionError (v202411)Stay organized with collectionsSave and categorize content based on your preferences.
AI-generated Key Takeaways
ProposalActionError lists errors related to actions on Proposal objects within the ProposalService.
This error type inherits from ApiError and includes fields such as fieldPath and trigger.
ProposalActionError has a specific reason field represented by an enum, which can indicate issues like the operation not being applicable or the proposal being archived.
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 outlines the `ProposalService` and its associated error types, derived from `ApiError`. This includes a comprehensive list of specific errors, such as `AuthenticationError`, `ForecastError`, `ProposalError`, and many others related to various aspects like billing, currency, fields, and quotas. Additionally, `ProposalActionError` specifies errors tied to proposal state, like `NOT_APPLICABLE` and `IS_ARCHIVED`. The document defines how these errors are represented with fields like `fieldPath`, `trigger`, and `errorString`.\n"]]
