CDS pluginCDS pluginInstalls 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 →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
dynamic-external-cds-join
A CAP plugin for SaaS extension scenarios that joins external entities with internal tables at query time; its declared repository is not publicly reachable.
Facts
Latestv1.0.1ReleasedLicenceApache License 2.0, January 2004
Where it sits
Lives in
Provides
Tenant extensibilityCAPTenant extensibilityLetting a customer extend the model of a running SaaS application with extra fields and entities per tenant, without forking the application, as distinct from extending the application's code for every customer at once.
Flavors
Node.jsfrom its runtime
Requires
@sap/cds≥ 8@sap/cdsThe peer range, as published.
Who is behind it
venkatesh-hulekal
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.
PracticalFunctional boundary
The declared repository is on SAP's internal GitHub (github.tools.sap) and is not publicly reachable, so npm is the only place to read anything about it.
What it declares
Every artifact
- Type
- CDS plugin
- Origin
- Independently maintained
- Runtime
- Node.js
As a CDS plugin
- Declared for
- >=8
- Distributed through
- does not say
Connections
Group by
NodeRelationBasis
Functional
Tenant extensibilityTenant extensibilityLetting a customer extend a running SaaS model per tenantSAP and community, unassessed
provides
authored
provides Tenant extensibility
Letting a customer extend a running SaaS model per tenant
Download
Install
npm add dynamic-external-cds-joinDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from dynamic-external-cds-join@1.0.1 under MIT, readHistory
Others providing
Compare all 2 on the Tenant extensibility page →Tenant extensibilityTenant extensibilityLetting a customer extend the model of a running SaaS application with extra fields and entities per tenant, without forking the application, as distinct from extending the application's code for every customer at once.SAP and community, unassessed
- @sap/cds-mtxs@sap/cds-mtxsMultitenancy, tenant provisioning and model extensibility for CAP.sap official, capMultitenancy, tenant provisioning and extensibility for CAPfrom CAP
Details
Sources
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
declared for>=8
latestv1.0.1
first release
releases and cadence2
discovered vianpm registry · keywords:cds
first seen in the atlas
ecosystem and domaincap, data-and-persistence
History in the atlas
- First seen.
For your agent
- Ref
artifact:venkatesh-hulekal-dynamic-external-cds-join- JSON
- /artifacts/venkatesh-hulekal-dynamic-external-cds-join.json
- MCP
- Connecting an agent