update_prime_change_order
Modify a prime change order in Procore to update contract details, status, dates, and financial information for construction project management.
Instructions
Update Prime Change Order. [Construction Financials/Prime Contracts] PATCH /rest/v1.0/projects/{project_id}/prime_change_orders/{id}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Unique identifier for the project. | |
| id | Yes | ID of the Prime Change Order | |
| run_configurable_validations | No | If true, validations are run for the corresponding Configurable Field Set. | |
| view | No | Specifies Which view (which attributes) of the resource is going to be present in the response. the extended view includes change events data, while the default view does not. | |
| contract_id | No | Unique identifier for the contract. | |
| batch_id | No | Unique identifier for a change order batch. | |
| change_order_change_reason_id | No | Unique identifier for the change reason. | |
| location_id | No | Unique identifier for the location. | |
| designated_reviewer_id | No | Unique identifier for the designated reviewer. This field is only supported for single-tier projects. Behavior is undefined in multi-tier projects. | |
| received_from_id | No | Unique identifier for the received from entity. | |
| description | No | Description | |
| due_date | No | Due Date | |
| paid_date | No | Paid Date | |
| invoiced_date | No | Invoiced Date | |
| title | No | Title of the Contract | |
| status | No | Status | |
| reference | No | Reference | |
| number | No | Number of the Change Order | |
| revision | No | Revision Number | |
| field_change | No | Field Change | |
| signature_required | No | Whether a signature will be required for this Change Order | |
| signed_change_order_received_date | No | Signed Change Order Received Date | |
| schedule_impact_amount | No | Schedule impact in days | |
| executed | No | Whether or not the Change Order is executed | |
| private | No | Whether or not the Commitment Change Order is private | |
| paid | No | Whether or not the Commitment Change Order is paid | |
| reason | No | Reason for the change order | |
| custom_field_%{custom_field_definition_id} | No | Value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ... | |
| enable_ssov | No | Whether to enable SSOV on this Change Order. Only applicable to Commitment Change Orders. | |
| change_event_attachment_ids | No | List of attachment IDs to attach. These must presently be associated with Change Events. | |
| attachment_ids | No | Existing attachments to preserve on the response | |
| drawing_revision_ids | No | Drawing Revisions to attach to the response |