Update Viewpoint Mapping And/Or Model Manager Viewpoint Content (REST V2.0)
update_viewpoint_mapping_and_or_model_manager_viewpoint_contentUpdates viewpoint mapping (primary/position) on a coordination issue and optionally patches Model Manager viewpoint fields by merging camera, redlines, sections, visibility, or sending a full payload.
Instructions
Updates the MM-backed mapping (viewpoint_id = viewpoint_uuid): primary and position on bim_viewpoints_coordination_issues, and optionally name / payload fields via Model Manager PATCH. Discrete fields (camera_data, sections_data, redlines_data, visibility, render_mode) are merged into the current MM payload after loading the viewpoint from Model Manager, unless payload is sent (full replace of MM payload). Parity keys such as scene_id / **`bim_mo... Use this to update an existing Coordination Issues (only the supplied fields are changed). Updates the specified Coordination Issues and returns the modified object on success. Required parameters: company_id, project_id, coordination_issue_id, viewpoint_id. Procore API (v2.0): Project Management > Coordination Issues. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/{coordination_issue_id}/viewpoints/{viewpoint_id}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company_id | Yes | URL path parameter — unique identifier for the company. | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| coordination_issue_id | Yes | URL path parameter — coordination Issue ID | |
| viewpoint_id | Yes | URL path parameter — **MM-backed:** Model Manager viewpoint UUID (`[0-9a-f-]{36}`, case-insensitive). **Legacy:** numeric `bim_viewpoints.id` for a join row that has `bim_viewpoint_id` (no `viewpoint_uuid`). | |
| name | No | JSON request body field — passed to Model Manager viewpoint PATCH (`name`) when provided. | |
| scene_id | No | JSON request body field — accepted but not applied on PATCH (create-only relocation). | |
| bim_model_uuid | No | JSON request body field — accepted but not applied on PATCH. | |
| payload | No | JSON request body field — the payload for this Coordination Issues operation | |
| camera_data | No | JSON request body field — when `payload` is absent — merged into MM payload as `camera` (object or JSON string). | |
| redlines_data | No | JSON request body field — when `payload` is absent — merged into MM payload as `markup`. | |
| sections_data | No | JSON request body field — when `payload` is absent — merged into MM payload as `clipping.planes`. | |
| render_mode | No | JSON request body field — the render mode for this Coordination Issues operation | |
| bim_file_id | No | JSON request body field — accepted but not applied on this PATCH flow. | |
| bim_view_folder_id | No | JSON request body field — accepted but not applied on this PATCH flow. | |
| snapshot_upload_uuid | No | JSON request body field — accepted but not applied on this PATCH flow. | |
| primary | No | JSON request body field — sets `is_primary` on the coordination-issue viewpoint mapping. | |
| position | No | JSON request body field — sort order on the join row; send `null` to clear when supported by validation. | |
| visibility | No | JSON request body field — the visibility for this Coordination Issues operation |