Getting realistic data into a service so it can be developed and demonstrated — initial data, per-tenant content, and believable volumes for testing.
Not covered: It stops at shape, not volume. cds add data fills the right columns with placeholder values; it does not make a name look like a name or an IBAN like an IBAN, and it has no notion of per-tenant fixtures.
Community generators fill db/data with believable values: cap-js-mockdatacap-js-mockdataA cds add command that generates CSV seed files into db/data from @Mockdata annotations on your entities, filling each column with values from the Faker module the annotation names.independent, cap from @Mockdata annotations with Faker, and cap-mock-generatorcap-mock-generatorParses the .cds schema and fills db/data with relationally consistent CSV — through an LLM layer where one is configured, or a local engine where none is.independent, cap from the .cds schema, with relationally consistent rows. @sap/cds-common-content@sap/cds-common-contentISO-standard content for CAP's common definitions — countries, languages, currencies and timezones — so a project does not seed those tables itself.sap official, cap is SAP's ISO content for the common countries, currencies, languages and timezones, and @animb1996/cds-data-drift@animb1996/cds-data-driftCompares the CSV files under a CAP project's db/data with the rows in the database bound as its db service, and reports where the two have diverged without writing to either.independent, cap reports where the CSV files and the deployed rows have diverged.
cds add data arrived, generating seed files with a record count per entity and a CSV or JSON target. Before it, the core loaded CSV but did not produce any. The 7.9 line reached npm on 2024-05-02.
Any guidance that you must hand-write or third-party-generate CSV to get seed data at all. That was true before mid-2024 and is not now — the open question is realism, not volume.
capability:seed-data