1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| shd-safe-bulk-change | Use before any SHD bulk create, update, import, archive, delete, or other multi-record mutation, and whenever the user asks to plan a mass change. |
Safe SHD bulk changes
Plan first
- Confirm the target module, organization/project scope, exact match rule and intended side effect.
- Read current schemas and records. Estimate affected, skipped, invalid and ambiguous rows.
- Prefer a server validation or dry-run operation. For ProjectBase use
shd_project_db_validate_records, thenshd_project_db_bulk_create_recordsorshd_project_db_bulk_upsert_recordswithdry_run: truewhen applicable. - Present the plan and stop unless the user explicitly authorized execution.
Execute safely
Use stable idempotency keys, expected versions and exact match fields accepted by the selected tool. Do not silently widen a project, organization, table or record filter. Do not convert a failed or conflicting row into a new record.
After execution, report created, updated, skipped, rejected and conflicted rows, then use the server's persisted readback when available. Destructive operations require explicit confirmation and remain subject to server ACL.
See references/write-preflight.md for the required preflight record.