Change several capex proposals at once, each exactly as save_capex_plan_line changes one.
Change several capex proposals at once, each exactly as save_capex_plan_line changes one.
p_lines is a list of proposals, each an object holding the proposal’s id and any of these fields, named as its columns are: name, coordinator_user_id, quantity, priority, capex_nature_id, category_master_id (the Category), budget_category_id (the Sub-Category), fresh_sanction_amount and approved_carryover_amount. A field left out keeps what the proposal holds, and every other field of the proposal — its justification, item detail, unit, location, cost centre and Proposal ID among them — is kept as it is. Any other field is refused with INVALID_LINE. A fresh-money proposal is asked the fresh sanction amount and a carry forward the approved carryover, and the other one is refused; the proposal’s value is then the amount its type asks. At most 1,000 proposals.
Each proposal is saved or refused on its own, with every check and permission save_capex_plan_line applies: changing one needs finance.capex_scheme.edit, or finance.capex_scheme.create for a proposal sent back to you for revision, and the proposal must still be open to change. What your organisation sets on the proposal form in the Form Studio applies too: a field it insists on is refused emptied with REQUIRED_FIELD_CLEARED, and a field whose writing it keeps to some roles is refused with FIELD_NOT_PERMITTED to anybody without one of them who changes it. A refused proposal is left as it was and the others are still saved.
Returns one row per proposal sent, in the order sent: line_id, scheme_code (its Proposal ID), ok, changed (the columns saving it changed, empty where it already held what was sent), and for a refused proposal the refusal’s error_code, message, hint and detail. A proposal that cannot be found, or is on a plan you cannot reach, is refused with NO_SUCH_LINE, and one sent twice is saved once, the second refused with DUPLICATE_LINE.
Headers
Preference
params=single-object Body
Change several capex proposals at once, each exactly as save_capex_plan_line changes one.
p_lines is a list of proposals, each an object holding the proposal's id and any of these fields, named as its columns are: name, coordinator_user_id, quantity, priority, capex_nature_id, category_master_id (the Category), budget_category_id (the Sub-Category), fresh_sanction_amount and approved_carryover_amount. A field left out keeps what the proposal holds, and every other field of the proposal — its justification, item detail, unit, location, cost centre and Proposal ID among them — is kept as it is. Any other field is refused with INVALID_LINE. A fresh-money proposal is asked the fresh sanction amount and a carry forward the approved carryover, and the other one is refused; the proposal's value is then the amount its type asks. At most 1,000 proposals.
Each proposal is saved or refused on its own, with every check and permission save_capex_plan_line applies: changing one needs finance.capex_scheme.edit, or finance.capex_scheme.create for a proposal sent back to you for revision, and the proposal must still be open to change. What your organisation sets on the proposal form in the Form Studio applies too: a field it insists on is refused emptied with REQUIRED_FIELD_CLEARED, and a field whose writing it keeps to some roles is refused with FIELD_NOT_PERMITTED to anybody without one of them who changes it. A refused proposal is left as it was and the others are still saved.
Returns one row per proposal sent, in the order sent: line_id, scheme_code (its Proposal ID), ok, changed (the columns saving it changed, empty where it already held what was sent), and for a refused proposal the refusal's error_code, message, hint and detail. A proposal that cannot be found, or is on a plan you cannot reach, is refused with NO_SUCH_LINE, and one sent twice is saved once, the second refused with DUPLICATE_LINE.
Response
OK

