CaseTalk now exports to SAP Core Schema Notation (CSN) Interop Effective 1.2 format.

The export generates a .csn.json file using Generate Artifact. The output follows the official CSN Interop specification ([url=https://sap.github.io/csn-interop-specification/" rel="noopener,nofollow]https://sap.github.io/csn-interop-specification/[/url]) and is compatible with SAP Datasphere, SAP CAP, and other BTP tools that consume CSN.

Native CSN features used:

• CSN Interop Effective 1.2 document format
• Entity definitions with typed elements
• Primary key marking on key elements
• NOT NULL constraints
• CDS type system (cds.String, cds.Integer, cds.Decimal, cds.Boolean, cds.Date, cds.DateTime, etc.)
• Associations (cds.Association) for foreign key relationships with cardinality
• @EndUserText.label annotations for descriptions

CaseTalk-specific annotations (extending CSN with conceptual modeling metadata):

• @CaseTalk.valueConstraint (on type definitions): allowed values for enumerated domains, e.g. "Graduate, Student"
• @CaseTalk.uniqueKey.<name> (on entities): alternate/unique key as an array of column names, representing business keys that CSN has no native construct for
• @CaseTalk.isSubset (on associations): true when the foreign key enforces a subset constraint
• @CaseTalk.phrase (on associations): natural language reading of the relationship, e.g. "Student lives in City"
• @CaseTalk.fromColumns (on associations): source column name(s) of the foreign key
• @CaseTalk.toColumns (on associations): target column name(s) referenced by the foreign key

These annotations use the standard CSN custom annotation mechanism (@namespace.property) and do not conflict with SAP annotations. They preserve conceptual modeling semantics from FCO-IM that have no native CSN equivalent, enabling richer model exchange.

Resolved in current build. Available in Generate Artifact dialog under Schema category.