Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Angular error NG01002 means a call to setValue did not provide a value for every control registered in a FormGroup or FormArray. Add the missing value when you intend to replace the full form value; use patchValue when the update is intentionally partial.
What NG01002 means
Angular’s NG01002 documentation describes the key rule this way: “setValue is strict — it expects a value for every control.” The value you pass must match the registered form structure: a group needs a value for each control, and an array needs a value for each registered control.
This is a mismatch between the form’s controls and the value supplied to a form update. It is not a browser, network, or installation error.
Choose between setValue and patchValue
| Method | Use it when | What to supply |
|---|---|---|
setValue |
You intend to assign the full value. | A value for every registered control. |
patchValue |
You intend to update only some controls. | Values for the controls being changed. |
Angular recommends patchValue for partial updates. Do not switch methods automatically: if the operation is supposed to populate the whole form, fix the incomplete value instead. See the official FormGroup API and FormArray API.
#1 Best Overall
Fix NG01002 in a FormGroup
Compare the object passed to setValue with the group’s registered controls. For a group with first and last, this value is incomplete:
{ first: 'Nancy' }To set the full group value, supply both keys:
{ first: 'Nancy', last: 'Drew' }If only first should change, use a partial update instead:
formGroup.patchValue({ first: 'Nancy' });Fix NG01002 in a FormArray
Compare the incoming array with the array’s registered controls. If the form array has two controls, passing only one value is incomplete:
['Nancy']For a full update, provide a value for both controls, in their corresponding order:
Rank #3
['Nancy', 'Drew']Trace where the value becomes incomplete
- Read the control named in the error. Check whether it is registered in the form and whether the value passed to
setValueincludes it. - Inspect the value immediately before the call. Compare its object keys or array entries with the group’s controls or array’s registered controls.
- Check the value’s source. API responses and partial state updates may omit controls. An object spread can also produce an incomplete value if the source object lacks required keys.
- Choose the intended update. Map the source into a complete form value before calling
setValue, or usepatchValueif changing only some controls is intentional.
NG01002 is not a missing value accessor error
NG01002 is Angular’s “Missing Control Value” runtime error for an incomplete value supplied to a form update. It is different from NG01203, which concerns a missing custom-control value accessor.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
