JTBD-DO-04 · Data operations
Export records
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
on a deliberately narrow reading: Customer Data Operations v2 adds export-customer-records over the package's eight managed record sets — the import log and its receipts, the identities, the candidates, the links, the findings, the bulk runs and their receipts. The set is counted first with a complete read, the answer states the row count and the bound, a set larger than the bound refuses with EXPORT_WOULD_TRUNCATE instead of returning a short file, at most 10,000 rows, and an export writes nothing. tests/customer-data-operations-v2.test.js. Still partial, and the row's own word is the gap: business records (companies, contacts, opportunities) export through no endpoint, filters are exact-match only, and there is no CSV, no streaming and no scheduled export
Evidence
Proved by this test, which run on every push:
tests/customer-data-operations-v2.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 ships no authentication, 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
- Import records from CSV — partially supported
- Detect duplicates on import or entry — partially supported
- Merge two Companies or Contacts — partially supported
- Bulk update a set of records — partially 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