(Get to all the parts in this series via the series post.) What we have from part 2 is a simple project myproj/ which relies upon a simple reuse package @qmacro/common. That reuse package currently exists only within a workspace within the myproj/ project. In order to be able to use it elsewhere and share the reuse...

(Get to all the parts in this series via the series post.) In wrapping up the end of part 1 we looked forward to creating the simplest kind of reuse module, not only as an important fundamental building block but as a base for further understanding and exploration (especially when we start looking closer at...

I'm writing this short post so I can refer to it when I want to explain my use of services.cds when creating sample CDS models. I've found myself explaining multiple times across various blog posts1 so I thought it was time to fix that behaviour and write it once (more) and point to it. One of the axioms in CAP is...

01 Jan 2026 Part 1 An introduction 07 Jan 2026 Part 2 Creating a simple reuse package 14 Jan 2026 Part 3 Publishing the simple reuse package 21 Jan 2026 Part 4 ...

You know the drill: instead of inventing your own versions of core model building blocks over and over again, use common types and aspects for reuse, like this: using { managed, cuid, Currency } from '@sap/cds/common'; namespace qmacro; entity Books : managed, cuid { title : String; price : Decimal; currency :...

After Devtoberfest comes TechEd and the long tail of conferences that lead into the holiday season. Then comes the new year, and a restart of our long running live stream show "Hands-on SAP Dev" on the SAP Developers YouTube channel. We're starting 2026 off with an under-the-hood style mini-series exploring...

The November 2025 release of CAP heralded a beta version of Status-Transition Flows, moving us up yet another gear in the journey towards declarative nirvana. Background I wanted to try out this new significant feature, one which embodies and celebrates one of the key reasons to use CAP - the code is in the...

I'm taking some time to peruse the Conceptual Definition Language (CDL) topic of the CAP documentation, and stopped at the first example in the Keywords & Identifiers section, which piqued my interest. Let's put this in a file called db/keywords-and-identifiers.cds: namespace capire.bookshop; using { managed, cuid }...

As I mentioned in my Upcoming talks in autumn 2025 post recently, I'll be attending and speaking at UKISUG Connect. I have a couple of sessions, a hands-on workshop on the Sunday and a technical track talk on the Monday. In this post I want to describe the hands-on workshop, what to expect, and (if you intend to...

Background I watched Mauricio Lauffer's Devtoberfest session Testing SAP CAP Node.js apps with cds.test yesterday, it was great. Thanks Mauricio! It's a nice accompaniment to the Testing with cds.test topic in Capire. Setting up a test project I set up a small project to try things out myself (using CAP Node.js,...

Background There's a classic structure often found representing business data in enterprise software, and that's the "document". Purchase requisition, sales order, goods receipt, and so on. Header and items. Most of the time the items don't make sense existing on their own, independent of their header parent. Such...

Background Recently the home for Capire documentation and sample repositories moved into the capire organisation on GitHub. This content includes classic modules such as bookshop which are now maintained as individual repositories, are subject to release schedules and deployments, and are made available as packages...