We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:
At the end of the article, you will find a set of instructions on how to update to the new versions.
Java Libraries: Release Highlights 3.17.1
You can update your dependencies of the SAP Cloud SDK for Java to version 3.17.1 and consume the new version from Maven Central.
OData Deep Update
With this release, we introduce support for OData v4 – Deep Update. Single and collection-based entity navigation properties can be used when updating a base entity. This way nested entities can be updated and created, while performing a single OData request. Currently, this feature can only be used with
modifyingEntity() and not with
replacingEntity(). Also removing an existing element from a collection-based entity navigation property is not yet supported.
The OData v4 Virtual Data Model (VDM) now supports ordering by multiple fields through calling the method
orderBy() and passing fields in corresponding order. The results will be ordered by this fields.
Several further improvements are listed in the full release notes.
We added support for setting additional parameters for OData queries, using the method
As usual, the full release notes contain a list of all improvements in this release.
How to Update
To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:
- Open the pom.xml file in the root folder of your project.
- Locate the dependency management section and therein the
- Update the version of that dependency to
With this, you are already done thanks to the “bill of material” (BOM) approach. Your dependency should look like this:
<dependencyManagement> <dependencies> <dependency> <groupId>com.sap.cloud.sdk</groupId> <artifactId>sdk-bom</artifactId> <version>3.17.1</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> <!-- possibly further managed dependencies ... --> </dependencyManagement>
If you update from a version prior to 3.0.0, have a look at our migration guide.
If you are using the SAP Cloud SDK in a project of the SAP Cloud Application Programming Model, replace
sdk-modules-bom to only update the version of SDK modules, not further dependencies.
You can now recompile your project (be aware of the compatibility notes, though) and leverage the new features of the SAP Cloud SDK in version 3.17.1.
Of course, you can also generate a new project that uses version 3.17.1 from the start by running the Maven archetypes for Neo or Cloud Foundry with
npm update in the root folder of your module. Note that this will also update other modules, unless you explicitly specify which packages to update. If you want to check beforehand what will change, use
Continuous Delivery Toolkit
If you are using the pipeline with a fixed version (as recommended since v7), update the continuous delivery toolkit with the following command, that you run on the server hosting the cx-server:
./cx-server update image
Learn more about SAP Cloud SDK
To learn how others in the community use SAP Cloud SDK you can check out more related blog posts.
Are you interested in a particular topic? It might be helpful to search the Q&A place? Feel free to ask your question there and do not forget to select the tag
SAP Cloud SDK.
If you are new to SAP Cloud SDK, get started and gain first hand-on exercise by following our tutorials.