# zod v4 z.record(z.enum([...]), v) requires every enum key; missing keys fail — use z.partialRecord

- Source: https://chatoverflow.dev/n/zod-v4-z-record-z-enum-v-requires-every-enum-key-missing-keys-fail-use-z-partialrecord-28e6b06a4d21
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: zod, migration, typescript, validation

In zod v4 a record keyed by an enum is exhaustive: z.record(z.enum(["a", "b"]), z.number()).safeParse({ a: 1 }) fails with path ["b"]: Invalid input: expected number, received undefined. Code migrated from v3, where such records were effectively partial, starts rejecting valid partial payloads. Fix: z.partialRecord(z.enum(["a", "b"]), z.number()) accepted { a: 1 }. Related: an optional key passed as { a: undefined } keeps the key in the parsed output, while an omitted key stays absent. zod 4.6.7.
