SAP Community - DJ Adams

Re: June Developer Challenge - CAP Knowledge - Analysis

2026-06-15T07:43:13.916000+02:00

By the way, if anyone would like a "starter" OData query URL to see their responses, here's one which I'm sure @YLN has come up with already - a way to find your own results for the questions to which you've responded. Here is an example, using @YLN as an example:

https://developer-challenge-june-2026.cfapps.eu10.hana.ondemand.com/odata/v4/main/Questions?$expand=responses($filter=communityID eq 'YLN')&$filter=responses/communityID eq 'YLN'

This uses a $filter query option both at the primary resource level but also within an expanded navigation property context.

Re: June Developer Challenge - CAP Knowledge - Analysis

2026-06-15T09:00:35.021000+02:00

@SachinArtani it is not case sensitive. I even point out that any case can be used, in the detailed instructions (see screenshot below). Here's the relevant line in the implementation:

const communityid = req.headers.communityid?.toLowerCase()

I tried with your community ID in all lower case, and it worked fine, returning the same hash value to what's returned when "SachinArtani" is used.

When you say "I tried ... it failed" - can you be more specific? "it failed" isn't much to go on 😉

June Developer Challenge - CAP Knowledge - Task 12 - Query mode in cds REPL

2026-06-16T07:00:00.033000+02:00

The cds REPL is a powerful facility that helps us explore and debug. It's based on the regular Node.js REPL, which has a number of REPL-level commands:

; node
Welcome to Node.js v24.15.0.
Type ".help" for more information.
> .help
.break    Sometimes you get stuck, this gets you out
.clear    Alias for .break
.editor   Enter editor mode
.exit     Exit the REPL
.help     Print this help message
.load     Load JS from a file into the REPL session
.save     Save all evaluated commands in this REPL session to a file

Press Ctrl+C to abort current expression, Ctrl+D to exit the REPL

The cds REPL extends the Node.js REPL with various commands, two of which have been available for a good while:

.inspect   Sets options for util.inspect, e.g. `.inspect .depth=1`.
.run       Runs a cds server from a given CAP project folder, or module name like @capire/bookshop.

Recently (in a CAP release earlier this year) the cds REPL gained a new "query mode" command, which enables us to write queries directly. In other words, instead of this:

> await cds.ql`SELECT from Books {title, price}`

we can, within the new query mode, write simply:

cql> select from Books {title, price}

What is the cds REPL command to enter this new query mode?

This is a question from the June Developer Challenge on CAP Knowledge. And don't forget: always submit your answer as a hash, on its own - read the Taking part section of the intro post for more info. At the end of today, this question will be updated with links to further reading on this topic.

Further info:

The new command was announced in the Query Mode in cds repl section of the February 2026 release notes.
You can read more about this new mode in the Trying it with cds repl section of the CXL topic.
For an introduction to the cds REPL, see the blog post Level up your CAP skills by learning how to use the cds REPL.
For a deeper dive into the cds REPL, with examples, see the blog post A reCAP intro to the cds REPL.

Re: June Developer Challenge - CAP Knowledge - Analysis

2026-06-16T07:06:31.407000+02:00

Hi @aelghannam - you're welcome! It just means that you are not quite in sync with the mechanism that gathers the responses and produces the analysis (e.g. you only posted a response to last Friday's question yesterday). You're on the list now, as the mechanism has just been rerun (as I mentioned in this post - updated daily). Cheers and good work!

Re: June Developer Challenge - CAP Knowledge - Analysis

2026-06-16T09:23:57.745000+02:00

@SachinArtani if you had provided some more detail than "it failed" in the first place, I would have perhaps known you meant the OData service rather than the hashing API 😉

Generally OData service system query option $filter, especially when used with the eq operator, is case-sensitive, by design. See https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_Equals for some details, for example.

The OData $search system query option is case-insensitive, but the use cases for this are slightly different of course. That said, you could retrieve the data you seem to be after like this:

https://developer-challenge-june-2026.cfapps.eu10.hana.ondemand.com/odata/v4/main/Responses?$search=sachinartani&$expand=question

HTH

Re: June Developer Challenge - CAP Knowledge - Analysis

2026-06-17T06:58:37.425000+02:00

Excellent @SachinArtani ! I like that, thanks for sharing. I will use HTH even more now 🚀

June Developer Challenge - CAP Knowledge - Task 13 - Optional CDL keyword

2026-06-17T07:00:00.034000+02:00

When building our CDS model, we describe, amongst other things:

types
aspects
entities
services

The CDL for each of these objects is clear and simple. That's because of the intent behind the design of CDS as a whole, but also because there's a particular keyword that is optional in such definitions, and is usually omitted.

What is that keyword?

Further info:

The entire CDL topic in Capire has various notes on how this keyword is optional.

Re: June Developer Challenge - CAP Knowledge - Analysis

2026-06-17T17:58:09.987000+02:00

@SergioG_TX thanks for asking. Others are doing that, and I don't see any harm in it. There's no prize, except the glory of learning 🙂

June Developer Challenge - CAP Knowledge - Task 14 - Change tracking

2026-06-18T07:00:00.025000+02:00

In an earlier question in this challenge, we looked at the managed aspect in the context of common and reusable definitions. This aspect causes each entity to which it is assigned to gain four new elements thus:

createdAt  : Timestamp @cds.on.insert : $now;
createdBy  : User      @cds.on.insert : $user;
modifiedAt : Timestamp @cds.on.insert : $now  @cds.on.update : $now;
modifiedBy : User      @cds.on.insert : $user @cds.on.update : $user;

This is change tracking at a very simple level, and often is all that is required.

But when more capable change tracking facilities are needed, there is a plugin that can be employed, which provides out-of-the-box support for automated capturing, storing, and viewing of the change records of modelled entities.

All one has to do, beyond installing the plugin as a dependency, is to annotate the parts of the model for which we want to have changes tracked.

What is the name of the annotation?

Further info:

See the Change Tracking section of the Plugins topic in Capire for an overview.
The plugin source repository on GitHub has a lot more detail.

June Developer Challenge - CAP Knowledge - Task 15 - Local binding registry

2026-06-19T07:00:00.138000+02:00

When embracing local-first development and using cds watch, we're actually using a convenience shortcut for:

cds serve all --with-mocks --in-memory?

That --with-mocks option for cds serve is described thus:

--with-mocks

  Use this in combination with the variants serving multiple services.
  It starts in-process mock services for all required services configured
  in package.json#cds.requires, which don't have external bindings
  in the current process environment.
  Note that by default, this feature is disabled in production and must be
  enabled with configuration 'features.mocked_bindings=true'.

Details of services that are provided by such server processes (or servers involved explicitly via cds mock, which is essentially another convenience shortcut for cds serve --mocked ...) are written to a special binding file which is for local-development only.

This binding file, also referred to as the "registry", is also read by other local server processes which require services, to see what's already available.

Technically the use of the bindings file is from --with-bindings which is described thus:

--with-bindings

  Use this option in local tests, to have all services provided by a
  process registered with their physical urls in a temporary file.
  All required services are bound automatically upon bootstrapping.
  Option --with-mocks subsumes this option.

i.e. if --with-mocks is used, then --with-bindings is implicit.

We can tell that this registry is for local-development just by looking at the file's location and name. Its location is in the developer user's home directory (very un-cloud-like), and its name starts with a dot (.), indicating it's a hidden file.

What is this file's name (don't include any directory prefix parts to it)?

Further info:

The Run Local with Mocks section of the Consuming Services topic in Capire has some practical information on how this registry is used.
For reference, see the Automatic Bindings by cds watch section of the Reuse and Compose topic in Capire.

June Developer Challenge - CAP Knowledge - Task 16 - Escaped names

2026-06-22T07:00:00.051000+02:00

As in most contexts, there are some name restrictions in the underlying database systems, with regards to unusual or special characters, or reserved words. When you use names like this in your CDS models they are escaped when they're converted to the equivalent DDL, and in all queries sent to the database.

The names are escaped in the DDL by enclosing them in double quotes. Here's an example:

CREATE TABLE BadNames (
  "a name" NVARCHAR(255),
  "drôle"  NVARCHAR(255),
  "select" NVARCHAR(255),
  "group"  NVARCHAR(255)
);

While it's not good practice to define element names like this, CDS allows for such definitions.

Take the first element in this DDL definition: "a name". To express this name, which contains whitespace, in the CDS model, it would also need to be escaped. Not using double quotes as above, but using the CDS model convention.

In other words, here's what the CDS model source might have started out looking like:

entity BadNames {
  SOMETHING : String;
}

But what would have needed to appear in place of the SOMETHING here?

Further info:

The CDL ⇒ DDL Translation section of Capire's CDL Compilation to Database-Specific DDLs topic contains lots of interesting detail here, including a subsection on invalid names.

June Developer Challenge - CAP Knowledge - Task 17 - Schema evolution testing

2026-06-23T07:00:00.033000+02:00

When thinking about schema evolution and starting to plan changes while still in development, the "drop-create" strategy is common.

The cds deploy command will generate the appropriate SQL/DDL statements to effect schema changes. Most commonly this command is run in the planning stages with an option to allow the to-be-executed SQL/DDL statements to be checked, but not executed.

What is that option?

Further info:

See the Schema Evolution topic in Capire.

June Developer Challenge - CAP Knowledge - Task 18 - RFC for UUIDs

2026-06-24T07:00:00.021000+02:00

The Internet Engineering Task Force (IETF) is the premier standards development organisation for the Internet. One of the ways that their work finds its way to the public in general and to engineers and techninians in particular is via documents, specifically RFCs (RFC stood originally for Requests For Comments). Each one is numbered and they describe fundamentals of the Internet, with RFCs ranging from core building blocks such as TCP/IP:

RFC 793 Transmission Control Protocol (TCP)
RFC 791 Internet Protocol (IP)

protocols that you and I deal with more closely and regularly, such as:

RFC2616 HTTP/1.1

as well as somewhat more "unusual" protocols, such as RFC1149, and even non-protocol defining RFCs such as:

RFC2119 Key words for use in RFCs to Indicate Requirement Levels

which is as wonderful as it is useful and meta.

RFCs remain essential to how and why things work.

In CDS modelling there are many built-in types, such as Boolean, Integer, DateTime and more. One of these built-in types is UUID, the type behind the common aspect cuid, which is defined thus:

aspect cuid {
  key ID : UUID;
}

This built-in type UUID is compliant with a specific standard described in an RFC document. What is that RFC document's number?

Further info:

The Core / Built-in Types topic in Capire has the list of types and links to reuse types and aspects (which includes cuid) as well as how the types relate to e.g. OData and HANA types.

June Developer Challenge - CAP Knowledge - Task 19 - CDS source formatter

2026-06-25T07:00:00.022000+02:00

There is great support for CAP development in IDEs such as VS Code and IntelliJ. Moreover, because the editor features for CDS are made available in the form of a language server (using the Language Server Protocol or LSP), they can also be used in other IDEs and editors, such as Neovim.

The CDS language server can be installed globally with:

npm i -g @sap/cds-lsp

Why would you do this? Well, for one thing, this gives us a very useful command line tool that can be used to format CDS source.

What is that command line tool called (the name of the command itself)?

Further info:

The Editors and IDEs topic in Capire has lots of information including a section on the CDS source formatter.
The blog post CDS source formatting and readability covers the CDS source formatter tool.

Re: June Developer Challenge - CAP Knowledge - Task 19 - CDS source formatter

2026-06-25T08:10:15.771000+02:00

@Dan_Wroblewski you are correct! Mea culpa. I've corrected the name to IntelliJ. Thanks!

On the question, I've added something to clarify*. Thanks also!

*although I thought that since the "human" name was in the title of this question, plus there are too many potential variations for that, folks would work out that it wasn't that which was sought 🙂

June Developer Challenge - CAP Knowledge - Task 20 - Compiler messages

2026-06-26T07:00:00.017000+02:00

The CDS compiler is a very capable mechanism and can advise and warn us if we present questionable design choices in our models. It can even refuse to continue in extreme circumstances.

Let's say we have a Book entity defined thus:

entity Book {
  key  id : String;
     isbn : String;
  content : String;
};

Then, in a service definition, we create a projection on that entity like this:

entity IsbnBook as projection on Book {
  *,
  isbn as id
};

The questionable design choice here is that with the isbn as id, we're effectively overwriting the id element that we're including by means of the * wildcard.

The compiler will issue a message with a severity level of Info for this. What is the message identifier (it is a three word phrase where the words are joined by dashes (-)?

June Developer Challenge - CAP Knowledge - Summary

2026-06-29T07:00:00.017000+02:00

Well, it's the end of the month, which means time for a wrap up of the Developer Challenge we've just had. It's been a lot of fun for us to create the questions and see how much you've all participated, and, from your comments, how much you've also enjoyed it. Thank you for taking part!

As you know, there are no prizes, the only reward is increased knowledge and understanding of a fundamentally important technology in the SAP developer universe. We'd love to hear from you (in comments to this post) what you thought, how you found the questions, whether you'd like to see something this again, and anything else that occurs to you.

Half way through the month, we published a brief analysis of your progress and success on the questions so far, and continued to update that on a daily basis. We've just run a final analysis update today (Sunday 28 June), which should have given you all enough time to answer the final question which was published at the beginning of last Friday. We've added a extra column to the table to show the answers too.

Facts, figures and heroes

Over the 20 questions you all submitted a total of 753 responses, which is fab! Thank you to everyone who did submit at least one response.

Bronze

In fact, here's a list of what we're going to call "Bronze" winners - everyone who participated:

AakankshaWs AfshanAnsari Andrii Anusha2025 Caisi Chaimae_Chairi27 Dan_Wroblewski FlorianP1 GauravPhadnis Greltel Guru_Charan HarshPatelV Henning Ihor_Haranichev JFenris Jawaharch Joery Laco M-Uzi MatLakaemper MattHarding Mayank_Mittal8 MioYasutake MohamedAbdelghany NakulG NeelimaEmmani NiklausB PVSBPrasadK PrabhuDC RajeshOlive Raphael Rupesh_Kumar25 SSaiSanthosh SachinArtani SergioG_TX Sushakude Swathi_SAP_Philomath SyamsundarKarukola VishnAndr YLN Yogananda _Jakub_ aelghannam ajmaradiaga ankitsrivastav aryan-11 berkaydurmaz berkayergun cayotteRizing ditt_kalyan furkan5 hrushikeshraju_yerram juancarlos_dasilva kasch-code lidavidlee mhameister milan_10 mvaibhav nagarjundas_1994 omer_sakar parthasaradhi sarvesh_agarwal satya01 shotokka shubhamkar soheil_st soisses stickman_0x00 sudarshan_b tchaitanya tobiasz_h

(Sorry we're not able to tag you all, the blogging platform limits the number of users one can mention in a single post to just 20).

Silver

There's a special subset of these participants who provided a response to every single question, well done and thank you for your perseverance and tenacity!

- @SachinArtani
- @shotokka
- @kasch-code
- @Swathi_SAP_Philomath
- @MatLakaemper
- @parthasaradhi
- @Dan_Wroblewski
- @Laco
- @ajmaradiaga
- @Anusha2025
- @VishnAndr
- @Joery
- @lidavidlee
- @Andrii
- @MioYasutake
- @berkaydurmaz
- @mvaibhav
- @Rupesh_Kumar25
- @furkan5

Gold

And there's an elite subset of the silver subset who not only provided a response to every single question, but got them all correct, amazing work, thank you and well done indeed! 🚀

- @SachinArtani
- @shotokka
- @kasch-code
- @MatLakaemper
- @parthasaradhi
- @Dan_Wroblewski
- @mvaibhav
- @furkan5

Wrapping up

Well, that just about wraps it up for this month's Developer Challenge. We hope you had fun, and learned something. Let us know also in the comments what you think of the CAP documentation that you've been exploring and studying over the last few weeks. We (and the CAP documentation folks) would love to know.

We'll keep the results OData v4 service online and available for the next few days, in case you want to do some analysis of your own.

Thanks everyone!

Re: June Developer Challenge - CAP Knowledge - Summary

2026-06-30T15:14:27.960000+02:00

Hi @aelghannam , done - the OData service is now updated (the rest of the stats will remain the same).

Re: 🐍 July Developer Challenge Week 1 — Model the Board

2026-07-04T15:09:04.440000+02:00

@STI_STI I like the way you added the @path annotation to the service to match the name in the URL path in Ajay's URL sample 🙂

SAP Developer News, July 9th, 2026

2026-07-09T21:00:00.015000+02:00

ITEMS

Live from WeAreDevelopers

- WeAreDevelopers World Congress https://www.wearedevelopers.com/world-congress

CAP June 2026 release (cds 10)

- Release notes https://cap.cloud.sap/docs/releases/2026/jun26

ABAP Cleaner in VS Code!

- https://marketplace.visualstudio.com/items?itemName=SAPOSS.abap-cleaner

Live streams at Code Connect next week

- Code Connect https://code-connect.dev/
- UI5con https://openui5.org/ui5con/
- UI5con agenda https://openui5.org/ui5con/program.html
- UI5con 2026 Live from the Main Stage https://www.youtube.com/live/CMPudw4scSE
- reCAP https://recap-conf.dev/
- reCAP agenda https://recap-conf.dev/program.html
- reCAP Live from the Main Stage https://broadcast.sap.com/go/reCAP
- reCAP 2026 - Streaming Sidetrack https://teams.microsoft.com/meet/347149883889697?p=ZkR4erzGjpPRtZ6zJh

Additional CAP highlights and MCP Gateway

- Building MCP Servers with SAP Integration Suite: What to Design, Not Just How to Connect https://community.sap.com/t5/technology-blog-posts-by-sap/building-mcp-servers-with-sap-integration-suite-what-to-design-not-just-how/ba-p/14435261
- Design APIs and MCP servers https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/design-apis?locale=en-US
- Release calendar for SAP Integration Suite https://me.sap.com/notes/3418154

Did You Know? #25 cds add test

- The cds add command https://cap.cloud.sap/docs/tools/cds-cli#cds-add

CHAPTER TITLES

00:00 Intro
00:07 Live from WeAreDevelopers
02:16 CAP June 2026 release (cds 10)
13:14 ABAP Cleaner in VS Code!
14:37 Live streams at Code Connect next week
15:05 Additional CAP highlights and MCP Gateway
17:20 DYK #25 cds add test

TRANSCRIPT

[Intro]
This is the Developer News for July 9th 2026.

[Tom, Sheena, Shilpa, Witalij]
Hi, we're coming to you this week from WeAreDevelopers conference in Berlin, which is a little bit of a difference for us developer advocates because we're actually mostly attending a conference instead of delivering one. So it's our opportunity to connect with other developers, particularly non-SAP developers from all around the world. I'm giving a session on Friday with Michael Ameling, where I'll be doing a preview of the new developers.sap.com that's all AI-powered - we'll show you more of in the coming weeks. What are the rest of you looking forward to?

Yeah we just now attended one session on Microsoft Fabric, it was really exciting, and we also got to know the latest advanced technologies that we can look forward to. So it was really exciting to be part of that session. The line was a little too long to get into the session.

That is the challenging part, to get into the sessions, but for me the interesting part is AI and agents because, it is not a surprise, but to be outside of the SAP ecosystem is what I'm interested in too, and get to learn more of what's happening outside of SAP.

So have you tried to find any sessions without AI or agents in the name?

No, all agents. I think that was the qualifier, probably. OK, and for me it's actually not the first time I'm attending this conference. I was here in 2019 and it is really good to be back here. This time SAP has a big presence here, we are actually one of the sponsors, we have our place on the show floor, we have our sessions as Thomas mentioned, he's going to do one with Michael Ameling but as well we have some other SAP colleagues delivering sessions based on the experience from their work, working with UI for example, and with user experience in this exciting AI era. So all in all, "no coffee, no code" but unfortunately the line for coffee is the longest one here, so if you don't see me coding this week, that's just because I cannot stand in this line and get my coffee.

[DJ]
cds 10 is out! That is, the next major release of the SAP Cloud Application Programming Model, also known as cds 10, was published last week.

This particular major release marks many milestones and is packed full of goodness.

Within the limitations of these news items, I can only give a brief overview, and you should definitely head over to the release notes which are very readable and full of details.

Some of the features and highlights are marked as Alpha or Beta ... so please pay attention to these status badges when working through the content.

Now, like other releases, the notes for this release are organised into different categories. There's the main major release upgrade category of course, a set of important highlights, notes on changes and improvements for both the Node.js and Java runtimes, and some updates for multitenancy services as well.

So, let's start with the very essence of this major release - the upgrade and migration context, and what tht implies.

Each of the packages that make up the entire framework have had major release version upgrades.
As the release notes say, don't mix old and new major versions. Instead, embrace change and try out the new cds upgrade tool which can help you.

The runtime support is also changing, with both Node.js and Java.

And before leaving this upgrade context, I must highlight the facilities that the CAP team have put together for this essential part of the software lifecycle - upgrades and migration. There's a new Migration Guide to help you get to cds 10 ... and a bleeding edge new 'cds upgrade' facility, in Alpha, to help with upgrades.

So next, let's have a look at some of the highlights, of which there are many in this release. Some of them are either in Alpha or Beta status, but they're there!

Let me enumerate them briefly. There's now support for aggregate data in hierarchies, useful for product catalogs, org charts, bills of materials and similar scenarios. It's available right now with the Java runtime, and support for Node.js is coming soon.

For VS Code users there's a new Project Explorer to help you visually navigate through your project and model's structures.

Now, while this has been hinted at before this advent of cds 10, there's a new protocol which I'm going to describe as "CAP native", and that's now available, and it's called HCQL - CQL conveyed over HTTP. Well suited for CAP-to-CAP integrations, and available just by adding an @hcql annotation, in the true CAP tradition of magic-made-simple.

There are early AI related goodies too, in the form of CAP-level (Calesi-style) agents, and also a CAP skills library, because, as we know, focusing on intent and best practice in development is essential.

There's a new Data Inspector, which comes in the form of a plugin and allows the controlled inspection of data in the entities exposed by your services.

Now, event queues in CAP have also been given lots of love, in the form of a new scheduling API, improved processing, and an overhaul of the documentation.

Now, last December we saw the first public Beta of the 'cds export' command which we can use to create API client packages from CDS service definitions. With this cds 10 release, that command is now generally available.

Now there are some more highlights in this cds 10 release, but my good friend and colleague Antonio is going to cover those in another news item in this news episode, so stay tuned!

Let me now turn to the Node.js runtime context where there are also plenty of items for us to celebrate.

First up, consolidated service APIs. What does that mean? Well, the generic CRUD (Create Read Update Delete) handler now returns the same shape of data for all write operations. That means app, db and HCQL-proxied remote services all look and behave the same way, which is great for uniform and minimised handler code variations.

Now, AI agents are great, but one thing they don't know much about is Fiori draft data. So working with active data has been simplified and consolidated - making it easier for everyone, us humans and our AI overlords, to work in a draft-first context.

A massive piece of work that the team has undertaken over the last months, culminating in what we have with cds 10, is a significant move towards a greater embrace of modern tools and native libraries. Very briefly - the testing framework Vitest is now used in favour of Jest, which will be abandoned longer term. ECMAScript Modules (that's ESM to you and me) is the official standardised system for packages and reuse, and CAP is now embracing that as the default module system. Third party dependencies are being dropped in favour of native or built-in alternatives. For example this calendar year already has seen a move to a Node-native SQLite driver (which replaces better-sqlite3) and to the Node-native Fetch API (which replaces Axios, and in development scenarios, also removes the need for the SAP Cloud SDK).

This work to embrace modern techniques, native libraries and the newest stable standards is fantastic. An important "side effect" is also something we can celebrate - a significantly reduced set of dependencies (and thus a smaller install footprint and code surface area).

Now last but certainly not least in the Node.js category is some news on the Telemetry plugin, which is now at version 2 after a major update which also brings support for OpenTelemetry SDK 2.0.

Next, let's look at the Java runtime category, which has now reached major version 5. Lots of new features, including, importantly, support for Spring Boot 4.

There are some new minimum versions of major dependencies that you need to take care of.

With CAP Java 5 there are some changes that are not backwards compatible (as in any major release), but the migration is made easier for us with a specific migration guide and OpenRewrite recipes for automated code adjustments.

Now, there are changes to CDS property defaults to align them with recommended settings for production use.

The API methods that were deprecated in the previous major release and marked as 'forRemoval' ... have now been removed.

CAP Java 5 now defaults to JDK 25, which is a long-term-support version. The SapMachine 25 JDK with the SAP Java buildpack is recommended.

With this new major CAP Java release, search is harmonised with both CAP Node.js and RAP, and by default uses the SAP HANA search syntax (for which there is now full support). Fuzzy search is also now enabled by default on SAP HANA, with improved support for UUIDs and large strings, and available in hierarchy queries.

Now, there's also much faster typed data access available. Instead of using a dynamic proxy to handle the underlying data map for accessor interfaces, it's now possible to have implementation classes generated. This resulting in up to 10 times the performance.

Previously, CAP Java used Apache's Olingo library for OData support. Following Olingo's retirement last year, there's now built-in support for OData, that's no mean feat! That of course also means fewer dependencies and it also brings improved performance.

There's also support for creating active versions of draft-enabled entities, similar to what we learned about earlier in the Node.js runtime context.

There are also plenty more features that come with CAP Java 5. Check them out in the release notes.

But to round out the release notes overview for this cds 10 version, there are a couple of points of note in the context of MTX services. First, there's now a stricter annotation validation for extensions. And second, migration support to go from @SAP/cds-mtx to @SAP/cds-mtxs has been removed.

That pretty much wraps up things for this June 2026 major release, congratulations to the entire CAP team for a huge set of new features and improvements. And don't forget to check out Antonio's item in this news episode for those other highlights.

[Rich]
Hey friends, Rich Heilman here. I hope everyone is staying cool, staying out of the heat. Good news for ABAP developers this week. ABAP Cleaner is now available as a VS Code extension, bringing its powerful code formatting capabilities out of Eclipse and into the modern editor of choice for many developers. So, what does it do? ABAP Cleaner applies over 100 rules to your code with a single keyboard shortcut. Automatically cleaning up formatting, modernising syntax, and even flagging unused variables. The result is clean and consistent code across your entire team without anyone having to argue about style. You can run it as a quick one-shot format, or drop into interactive mode to choose exactly which rules apply to your codebase. If your team already has a configuration setup in Eclipse, you can import those rule variants directly. No need to start from scratch. The setup does a Java runtime and a bit of environment variable configuration, but once it's running, you get the same functionality that ABAP developers have relied on in ADT in Eclipse - now in a much lighter, faster editor. If you're doing ABAP development in VS Code, this one's worth installing. Check it out today.

[Ajay]
Hello everyone. Code Connect is next week, from 13th to 16th July 2026. For all of you who cannot join us in person, there are live streams available for UI5con and reCAP, from the main stage. Please check out the agenda and streaming links available for UI5con and reCAP and join us online during the Code Connect event. Links to the live streams and agendas will be available in the description.

[Antonio]
¡Hola, SAP Developers. As you already know, the June 2026 CAP release is huge. DJ has already shared many of the highlights and I just want to mention a couple more. There is a new AI plugin, in Alpha, which simplifies integration with SAP AI Core. It will automatically resolve service bindings, manage resource groups, and AI model deployments. And it provides a standard AI Core service to interact with AI Core programatically. The new Data Privacy plugin, in Beta, for Node.js, which provides out of the box integration with the SAP Data Privacy Integration Service. Based on the personal data and ILM annotations in the data model the plugin will automatically expose two endpoints that can be consumed by the service. Now, related to the integration space, CAP Node.js now supports the Event Mesh capability in SAP Integration Suite, as an alternative to the standalone SAP Event Mesh, meaning that you can now easily use it as an event broken in your CAP applications. There is the new MCP Protocol Adapter, which allows exposing existing CAP services to AI agents and LLM powered as just another protocol. Just install the plugin and annotate services with @McP, et voila, your CAP service exposes MCP functionality. Extremely powerful and easy to implement. I already used it in a CAP service that I'm developing while I was getting familiar with the new feature of SAP Integration Suite. Yes, what we've all been waiting for - the new MCP Gateway is now available as part of Integration Suite. It is part of the new Integration Cell Runtime which is a cloud native runtime purposely built for designing, deploying and operating APIs and MCP servers. It is GA now and being rolled out in the Enhanced and Premium editions of SAP Integration Suite. Not just that, but it is also available in the BTP Trial environment. What are yoiu waiting for? Go check it out. Hasta luego!

[Ajay]
Did you know that cds add does generate the best practices of the test implementation of your CAP service? One can rapidly create a sample CAP project with cds init bookshop --add sample. Run cds add test in the terminal to add test suite files for all the defined CAP services in your existing project. It creates the latest boilerplate files and structures required for you to get started with your test implementation in a jiffy. For each services it generates a sample test for the GET request for an entity and a test for any action defined in the service. This also adds the test dependencies to your project. It uses the Node test runner for the tests. Install your dependencies and just run npm t to execute your tests. The generated test implementation does need to be tweaked for the valid test data. CAP also provides a command npx cds test to mute the verbose server output and lets you focus only on the failing tests. Use -u to unmute the server output when you do not need them. Enjoy your CAP tests!