bknd-crud-update_skill

Overview

This skill explains how to update existing records in a Bknd entity using the SDK or REST API. It covers single and bulk updates, relation operators ($set, $add, $remove, $unset), partial and conditional updates, response handling, and common patterns and pitfalls. Practical examples include React integration, optimistic updates, and verification steps.

How this skill works

Use api.data.updateOne(entity, id, data) to change a single record and api.data.updateMany(entity, where, data) for bulk updates. Relation changes use operators inside the field value (e.g., { tags: { $add: [4] } }, { author: { $unset: true } }). Responses return { ok, data, error } so you can verify success and read back the updated record if ok is true.

When to use it

• Update a single record after a form submission or admin edit
• Apply bulk changes by criteria (archive drafts, update statuses)
• Modify relations: add/remove links or replace entire relation sets
• Perform conditional updates only when business checks pass
• Implement optimistic UI updates with rollback on failure

Best practices

• Always check the response ok flag before using data
• Verify the target record and related IDs exist to avoid FK errors
• Use updateMany only with an explicit where clause to avoid accidental global changes
• Use $add/$remove for incremental relation changes and $set to replace
• Revalidate caches or mutate SWR keys after successful updates

Example use cases

• Switch a post status to published and set published_at with updateOne
• Add tags to a post without losing existing tags using { tags: { $add: [...] } }
• Archive all draft posts older than a date with updateMany and a where filter
• Implement an edit form in React that loads data, updates via api.data.updateOne, and shows errors
• Perform optimistic UI updates: update local state, call updateOne, rollback if ok is false