Why should you care?

Form “Save profile” screens sometimes send the full object. Replace makes the stored document match that snapshot exactly.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

db.users.insertOne({ username: "kabir", city: "Delhi", bio: "old", score: 10 })
db.users.replaceOne(
  { username: "kabir" },
  { username: "kabir", city: "Mumbai", level: "pro" }
)
db.users.findOne({ username: "kabir" })

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• After replaceOne, bio and score are gone because they were not in the replacement document.
• city is Mumbai and level is new.
• _id stays the same.

Practice next

1. Insert kabir and replace as shown.
2. Confirm bio is missing.
3. Contrast with updateOne $set that keeps bio.
4. Replace again adding bio back.
5. Compare matchedCount when filter misses.

Remember

replaceOne overwrites the whole document. Omitted fields disappear. _id is preserved.

Admin edits full tenant config

A SaaS settings page posts the entire config object; the API replaceOne’s the tenants document.

Outcome: Removed toggles truly disappear instead of lingering as stale fields.