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 error types related to proposal line items, particularly programmatic ones, within the `ProposalService`. These errors, inheriting from `ApiError`, cover various aspects like authentication, billing, custom fields, deals, forecasting, and proposal-specific issues. The `ProposalLineItemProgrammaticError` specifically details constraints for programmatic proposal line items. It lists reasons like invalid product types, unsupported video or roadblocking features, specific rate or creative rotation types, and invalid pricing models, highlighting restrictions on programmatic proposal configurations.\n"],null,[]]