JTBD-DO-01 · Data operations
Import records from CSV
partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
What the catalogue records
Customer Data Foundation v1 adds a bounded import under a fingerprinted mapping (customer-rows@1): a preview that provably writes nothing, a per-row receipt carrying an outcome and a reason code, counts that always reconcile (accepted + rejected + skipped == rows), an all-or-nothing or partial acceptance mode, and an idempotency key derived from the source system, the mapping fingerprint and the sorted row digests — never a clock or a random value, so the same import retried is the same run. examples/scenarios/customer-identity-governance.scenario.json, tests/customer-data-foundation.test.js. Still partial, and the row's own word is the gap: there is no CSV. The rows are a bounded JSON array a caller hands in, capped at 500, with no file upload, no delimiter/encoding/header inference, no column-mapping UI, no streaming and no resumable or scheduled import
Evidence
Proved by this test, which run on every push:
tests/customer-data-foundation.test.jsWhat this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Data operations
- Detect duplicates on import or entry — partially supported
- Merge two Companies or Contacts — partially supported
- Export records — not supported
- Bulk update a set of records — not supported
- Save and share a filtered view — not supported
- Search across modules — not supported
- See a unified activity timeline for a record — partially supported
- Attach notes or files to a record — not supported