CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →by a partnerby a partneroriginPublished by an SAP partner or vendor.See every one →

@rizing/cds-extension

A CAP extension, CDSX, that puts a draft-capable facade in front of an OData service imported into CAP, so Fiori elements can edit records that live in another system as drafts.

An OData service imported into a CAP project with cds import answers CRUD and nothing else, so a Fiori elements application projected onto it has no draft handling to bind to. CDSX supplies one: a shadow persistence entity declared in db/schema.cds mirrors the remote properties, @cdsx.api names the imported service on it, and the projection over it is marked @odata.draft.enabled, with the mirrored properties never written to the CAP table and only a property carrying @cdsx.extension persisted — an annotation the README marks experimental. Its own annotations cover what a remote service makes awkward from a draft: @cdsx.object.key generates a temporary value for a semantic key on draft creation, @cdsx.item.key numbers items from one, and @cdsx.datetime.persistency splits a timestamp into the separate date and time fields an ABAP stack persists. It is loaded by hand from cds.on('bootstrap') in server.js rather than through CAP's plugin mechanism, and its documentation states it is not intended to be used in conjunction with @sap/cds-odata-v2-adapter-proxy.

Facts

Latestv0.7.63ReleasedLicenceThe MIT License (MIT)

Where it sits

Lives in
Provides
Draft handlingCAPDraft handlingcapabilityLetting a user edit a record over several requests before it becomes real — saving unfinished changes, locking, and activating a completed draft.
Add-on to
@sap/cds@sap/cdsartifactThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.
Flavors
Node.jsfrom its runtime
Requires
@sap/cds@sap/cdsartifactCDSX is loaded into the CAP Node.js runtime from cds.on('bootstrap') to extend it with draft handling for imported OData services.

Who is behind it

Jhodel Cailan

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 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.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
CDS plugin
Origin
By a partner
Runtime
Node.js

As a CDS plugin

Distributed through
npm

Connections3

Install

npm add @rizing/cds-extension

Derived from the package name. No recipe recorded; the README has the configuration.

Learn more1

Readings
  1. Keep the Core Clean with Rizing CDSXJhodel Cailan, SAP Community

Where it sits in your app

Download
Your CAP application@rizing/cds-extension on npm, checked 2026-10-18: “Import OData V2 service metadata you want to consume from S/4HANA:”OData V2, outboundSAP S/4HANA, SAP solutionSAP S/4HANASAP solution@rizing/cds-extension, module@rizing/cds-extension
SAPnot SAP's, or the project's ownstated in the document

README

quoted from @rizing/cds-extension@0.7.63, read
@rizing/cds-extension@0.7.63/README.mdOn npm

Rizing CDSX

excerpt, The MIT License (MIT), read licencethe rest, on npm

History

Latest

v0.7.63

  1. v0.7.62

  2. v0.7.61

  3. v0.7.60

  4. v0.7.59

  5. v0.7.58

  6. v0.7.57

  7. v0.7.56

  8. v0.7.55

  9. v0.7.54

  10. v0.7.53

  11. v0.7.52

  12. v0.7.51

  13. v0.7.50

  14. v0.7.49

  15. v0.7.48

  16. v0.7.47

  17. v0.7.46

  18. v0.7.45

  19. v0.7.44

  20. v0.7.43

  21. v0.7.42

  22. v0.7.41

  23. v0.7.40

  24. v0.7.39

  25. v0.7.38

  26. v0.7.37

  27. v0.7.36

  28. v0.7.35

  29. v0.7.34

  30. v0.7.33

  31. v0.7.32

  32. v0.7.31

  33. v0.7.30

  34. v0.7.29

  35. v0.7.28

  36. v0.7.27

  37. v0.7.26

  38. v0.7.25

  39. v0.7.24

  40. v0.7.23

  41. v0.7.22

  42. v0.7.21

  43. v0.7.20

  44. v0.7.19

  45. v0.7.18

  46. v0.7.17

  47. v0.7.16

  48. v0.7.15

  49. v0.7.14

  50. v0.7.13

  51. v0.7.12

  52. v0.7.11

  53. v0.7.10

  54. v0.7.9

  55. v0.7.8

  56. v0.7.7

  57. v0.7.6

  58. v0.7.5

  59. v0.7.4

  60. v0.7.3

  61. v0.7.2

  62. v0.7.1

  63. v0.7.0

  64. v0.6.5

  65. v0.6.4

  66. v0.6.3

  67. v0.6.2

  68. v0.6.1

  69. v0.6.0

  70. v0.5.0

  71. v0.4.0

  72. v0.3.0

  73. v0.2.0

  74. v0.1.27

  75. v0.1.26

  76. v0.1.25

  77. v0.1.24

  78. v0.1.23

  79. v0.1.22

  80. v0.1.21

  81. v0.1.20

  82. v0.1.19

  83. v0.1.18

  84. v0.1.17

  85. v0.1.16

  86. v0.1.15

  87. v0.1.14

  88. v0.1.13

  89. v0.1.9

  90. v0.1.8

  91. v0.1.7

  92. v0.1.6

  93. v0.1.5

  94. v0.1.4

  95. v0.1.3

  96. v0.1.2

  97. v0.1.1

  98. v0.1.0

On npm
0downloads per week, npm
Weekly downloads for @rizing/cds-extension26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 0.27 Apr – 3 May: 2014 May – 10 May: 2011 May – 17 May: 11418 May – 24 May: 10525 May – 31 May: 61 Jun – 7 Jun: 1208 Jun – 14 Jun: 14815 Jun – 21 Jun: 20422 Jun – 28 Jun: 2529 Jun – 5 Jul: 56 Jul – 12 Jul: 5413 Jul – 19 Jul: 720 Jul – 26 Jul: 10827 Jul – 2 Aug: 73 Aug – 9 Aug: 20410 Aug – 16 Aug: 11417 Aug – 23 Aug: 624 Aug – 30 Aug: 1331 Aug – 6 Sept: 1117 Sept – 13 Sept: 12014 Sept – 20 Sept: 421 Sept – 27 Sept: 1228 Sept – 4 Oct: 35 Oct – 11 Oct: 10112 Oct – 18 Oct: 219 Oct – 25 Oct: 0
Draft handling
  1. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versions
  2. cap-handler-frameworkConvention-based handler layer for CAP with draft lifecycle hooks
  3. @sap/cds-fioriFiori draft handling and UI-facing behaviour for CAP services
  4. @sap/cdsCAP Node.js runtime
  5. cap-collaborative-draftCollaborative draft support for CAP Node.js services

Details

Sources3
npm registrydiscovered herechecked
npm registry, @rizing/cds-extensionversion, releases, installschecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
latestv0.7.63
first release
releases and cadence99, ~5d median
discovered vianpm registry
first seen in the atlas
ecosystem and domaincap, ui-and-frontend-bridge
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:rizing-cds-extension
JSON
/artifacts/rizing-cds-extension.json
MCP
Connecting an agent