---
id: ADR-CMT-MTG-004
title: Preserve Fields Omitted From Edits
product_area: committees
module: meetings
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d
decision: >-
  Partial edit bodies preserve omitted fields, clear explicitly empty nullable
  values and compare the record version, while nested document merging remains a
  separate unimplemented requirement.
constrains:
  - SVC-CMT-MTG-meetings
  - SVC-CMT-MTG-recruitment
  - DOM-CMT-MTG-001
  - DOM-CMT-MTG-005
  - DOM-CMT-MTG-006
origin: >-
  CMTE-M1 D1 (Andrew 2026-10-19 17:45 ET),
  services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#Decisions;
  CMTE-M3 plan A4
alternatives:
  - option: Require a complete replacement body.
    why_not: A partial form could erase fields it never displayed.
  - option: Ignore explicit empty values.
    why_not: Staff would have no way to remove an existing nullable value.
consequences:
  - >-
    A future screen can submit just the fields it edits, subject to request
    schema requirements.
  - >-
    Video details are still replaced as a whole document, despite the chosen
    policy to preserve unrelated nested values.
supersedes: []
evidence:
  - >-
    services-committees at 36129c24:
    modules/meetings/services/persistence/meetings.ts:rewriteMeetingDetails,
    meeting-series.ts:updateSeries;
    modules/recruitment/services/persistence/openings.ts, nominations.ts
---
# Preserve Fields Omitted From Edits

## Context

A form often edits only part of a record. Its save must not erase data that was outside the form’s scope; the cited product decision governs that behavior.

## Decision

Partial edit bodies preserve omitted fields, clear explicitly empty nullable values and compare the record version, while nested document merging remains a separate unimplemented requirement.

## Alternatives Considered

Require a complete replacement body. A partial form could erase fields it never displayed.

Ignore explicit empty values. Staff would have no way to remove an existing nullable value.

## Consequences

A future screen can submit just the fields it edits, subject to request schema requirements. Video details are still replaced as a whole document, despite the chosen policy to preserve unrelated nested values.