Importing and exporting table data
Getting a file somebody supplies, a spreadsheet, a CSV or a JSON dump, into tables with its columns mapped and its values checked, and getting table content back out as a file. Data shipped with an application for development and demonstration is seed dataSeed dataGetting realistic data into a service so it can be developed and demonstrated — initial data, per-tenant content, and believable volumes for testing.SAP and community, narrow by design.
Overview
No core answer is documented.
CSV files in a project are loaded into the database when it is deployed, which is seed dataSeed dataGetting realistic data into a service so it can be developed and demonstrated — initial data, per-tenant content, and believable volumes for testing.SAP and community, narrow by design rather than a file a user supplies to a running service; capire's database guide documents no runtime import of an uploaded file, so no core answer has been found for this concern in CAP.
The import side, as a service endpoint: a spreadsheet is uploaded to a running CAP service, parsed on the server and written into the CDS entity named in the request.
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysA covered CAP application exports SAP product data into a non-SAP product, especially systematically or at scale.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
The export side can become the data-extraction case named in section 1. File format alone does not decide it; destination, scale and the scoped interoperability purpose matter.
SAP Developer License Agreement 3.2 CAP →Artifacts
Seen working
Details
Coverage
For your agent
- Ref
capability:data-import-export- JSON
- /capabilities/data-import-export.json
- MCP
- Connecting an agent