Value normalisation

Making stored values consistent regardless of how they were typed — trimming the padding, fixing the case — declared on the model rather than repeated in every handler that writes.

Overview

SAP SHIPS

No core answer is documented.

Not covered: CAP validates on write and does not change what it stores. @assert.format will reject a value with a trailing space; nothing in the core removes it, so normalisation is a handler you write or a plugin you install.

An ABAP-era expectation more than a modern one — conversion exits did this, and people arriving from that world look for it. Both entries here are annotation-driven and by the same vendor, which is a thin base to call this settled.

Artifacts2

2 of 2 artifacts
ArtifactSignals
CDS plugins2
@neoimpulse/cap-js-trimCAP plugin stripping whitespace from strings on write via @cds.trim
Signals
none
@neoimpulse/cap-js-uppercaseCAP plugin uppercasing strings on write via @cds.uppercase
Signals
none

Details

Coverage
statecommunity only, CAP
assessed
For your agent
Ref
capability:value-normalisation
JSON
/capabilities/value-normalisation.json
MCP
Connecting an agent