Updating specific fields in Firebase - Step-by-Step Execution

Process Flow - Updating specific fields

Start

↓

Select Document

↓

Specify Fields to Update

↓

Send Update Request

↓

Database Applies Changes

↓

Confirm Update Success

↓

End

This flow shows how to update only certain fields in a Firebase document without changing the whole document.

Execution Sample

Firebase

docRef.update({
  age: 30,
  city: 'New York'
});

Updates only the 'age' and 'city' fields of the selected document.

Process Table

Step	Action	Fields Sent	Database State Before	Database State After	Result
1	Select document 'user123'	N/A	{name: 'Alice', age: 25, city: 'Boston'}	{name: 'Alice', age: 25, city: 'Boston'}	Document selected
2	Call update() with {age: 30, city: 'New York'}	{age: 30, city: 'New York'}	{name: 'Alice', age: 25, city: 'Boston'}	{name: 'Alice', age: 30, city: 'New York'}	Fields updated
3	Confirm update success	N/A	{name: 'Alice', age: 30, city: 'New York'}	{name: 'Alice', age: 30, city: 'New York'}	Update confirmed

💡 Update completes after specified fields are changed; other fields remain unchanged.

Status Tracker

Variable	Start	After Step 2	Final
docRef	Reference to 'user123'	Reference to 'user123'	Reference to 'user123'
age	25	30	30
city	'Boston'	'New York'	'New York'
name	'Alice'	'Alice'	'Alice'

Key Moments - 2 Insights

Why does the 'name' field stay the same after update?

Because update() changes only the specified fields (age and city). Fields not listed, like 'name', stay unchanged as shown in execution_table row 2.

What happens if you try to update a field that does not exist yet?

Firebase creates the new field with the given value. This is like adding a new key to the document, similar to how age and city were updated in the example.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'city' after step 2?

A 'Boston'

B 'New York'

C undefined

D 'Chicago'

💡 Hint

Check the 'Database State After' column in row 2 of the execution_table.

At which step does the database state actually change?

A Step 2

B Step 1

C Step 3

D No change occurs

💡 Hint

Look at the 'Database State After' column and see when fields are updated.

If you add a new field 'email' in the update call, what happens to the document?

A The document is replaced entirely with only 'email'

B The update fails because 'email' does not exist

C Only 'email' is added or updated, other fields stay the same

D All fields are deleted except 'email'

💡 Hint

Refer to the key_moments explanation about adding new fields.

Concept Snapshot

Firebase update() changes only specified fields in a document.
Unspecified fields remain unchanged.
New fields can be added by including them in update().
update() does not replace the whole document.
Use update() to modify parts without overwriting all data.

Full Transcript

This visual execution shows how Firebase updates specific fields in a document. First, a document is selected. Then, update() is called with only the fields to change. The database changes those fields but keeps others intact. The update is confirmed successful. This method avoids overwriting the entire document and allows adding new fields easily.

Practice

1. What does the update() method do in Firebase Firestore?

easy

A. It creates a new collection in Firestore.

B. It deletes the entire document from the collection.

C. It changes only specific fields in a document without overwriting the whole document.

D. It reads all documents in a collection.

Solution

1. Step 1: Understand the purpose of update()

   The update() method modifies only the fields you specify in an existing document.

2. Step 2: Compare with other methods

   Unlike set(), update() does not overwrite the entire document, preserving other fields.

3. Final Answer:

   It changes only specific fields in a document without overwriting the whole document. -> Option C

4. Quick Check:

   update() modifies specific fields only [OK]

Hint: update() changes fields without replacing the whole document [OK]

Common Mistakes:

• Thinking update() deletes documents
• Confusing update() with set() creating collections
• Believing update() reads data

2. Which of the following is the correct syntax to update the field age to 30 in a Firestore document reference docRef?

easy

A. docRef.update({ age: 30 });

B. docRef.set({ age: 30 });

C. docRef.update(age = 30);

D. docRef.modify({ age: 30 });

Solution

1. Step 1: Identify the correct method for updating fields

   The update() method is used to change specific fields without overwriting the document.

2. Step 2: Check syntax correctness

   The correct syntax is docRef.update({ age: 30 }); where the fields to update are passed as an object.

3. Final Answer:

   docRef.update({ age: 30 }); -> Option A

4. Quick Check:

   update() uses object with fields [OK]

Hint: Use update() with an object to change fields [OK]

Common Mistakes:

• Using set() which overwrites the document
• Using invalid syntax like update(age = 30)
• Using non-existent method modify()

3. Given this code snippet:

const docRef = firestore.collection('users').doc('user123');
docRef.update({ 'profile.name': 'Alice', 'profile.age': 28 });

What will happen if the document user123 does not exist?

medium

A. The update will fail with an error because the document does not exist.

B. The update will silently do nothing and return success.

C. The update will create the document with the specified fields.

D. The update will overwrite the entire document with the new fields.

Solution

1. Step 1: Understand update() behavior on non-existing documents

   The update() method requires the document to exist; otherwise, it throws an error.

2. Step 2: Analyze the code context

   Since user123 does not exist, the update call will fail with an error.

3. Final Answer:

   The update will fail with an error because the document does not exist. -> Option A

4. Quick Check:

   update() fails if document missing [OK]

Hint: update() needs existing document; else error occurs [OK]

Common Mistakes:

• Assuming update() creates documents
• Thinking update() silently succeeds
• Confusing update() with set() with merge

4. You try to update a nested field using this code:

docRef.update({ 'address.city': 'New York' });

But you get an error. What is the most likely cause?

medium

A. Dot notation is not supported for nested fields in update().

B. The document does not exist, so update() fails.

C. You must use set() instead of update() for nested fields.

D. The field name 'address.city' is invalid in Firestore.

Solution

1. Step 1: Recall update() requirements

   update() requires the document to exist; otherwise, it throws an error.

2. Step 2: Check dot notation support

   Dot notation is supported for nested fields in update(), so that is not the cause.

3. Step 3: Confirm field name validity

   Field names with dot notation are valid in Firestore for nested updates.

4. Final Answer:

   The document does not exist, so update() fails. -> Option B

5. Quick Check:

   update() fails if document missing, dot notation allowed [OK]

Hint: update() fails if document missing; dot notation is valid [OK]

Common Mistakes:

• Believing dot notation is unsupported
• Thinking set() is required for nested fields
• Assuming field names with dots are invalid

5. You want to update the nested field settings.notifications.email to false in a Firestore document. The document may or may not exist. Which code snippet correctly updates or creates the document without overwriting other fields?

hard

A. docRef.update({ 'settings.notifications.email': false });

B. docRef.set({ 'settings.notifications.email': false });

C. docRef.update({ settings: { notifications: { email: false } } });

D. docRef.set({ 'settings.notifications.email': false }, { merge: true });

Solution

1. Step 1: Understand update() vs set() with merge

   update() fails if the document does not exist. set() with { merge: true } creates or updates without overwriting.

2. Step 2: Analyze each option

   docRef.update({ 'settings.notifications.email': false }); fails if document missing. docRef.set({ 'settings.notifications.email': false }); overwrites entire document. docRef.set({ 'settings.notifications.email': false }, { merge: true }); correctly merges nested field. docRef.update({ settings: { notifications: { email: false } } }); incorrectly uses update() with nested object, which overwrites nested fields.

3. Final Answer:

   docRef.set({ 'settings.notifications.email': false }, { merge: true }); -> Option D

4. Quick Check:

   Use set() with merge:true to update or create safely [OK]

Hint: Use set() with merge:true to update nested fields safely [OK]

Common Mistakes:

• Using update() when document may not exist
• Using set() without merge, overwriting data
• Passing nested objects to update() causing overwrite