Skip to content

    Application Service Providers

    Class cds.ApplicationService is the default service provider implementation, adding generic handlers as introduced in the Cookbook guides on Providing Services, Localized Data and Temporal Data.

    cds.ApplicationService class

    class cds.ApplicationService extends cds.Service

    Localized Messages / i18n

    Generic Errors

    You can provide localized error messages for a growing number of runtime errors. To do so, they simply need to provide messages_<locale>.properties files into one of the valid, model-unrelated text bundles folders. That is, as these texts aren’t model related, the properties files are only searched for in the folders listed in cds.env.i18n.folders and not next to any model. The first matching file is used. See Where to Place Text Bundles? for more details.


    // i18n/
    MULTIPLE_ERRORS=Multiple errors occurred.
    // i18n/
    MULTIPLE_ERRORS=Es sind mehrere Fehler aufgetreten.

    Custom Errors

    You can define custom texts (incl. placeholders) and use them in the message API req.reject/error/info/warn(...). The respective text key is provided instead of the string message, and optional array of placeholder values are passed as the last parameter. Placeholder values can again be text keys in order to enable translatable text fragments.


    // i18n/
    ORDER_EXCEEDS_STOCK=The order of {0} books exceeds the stock by {1}
    // srv/catalog-service.js
    const cds = require('@sap/cds')
    module.exports = (srv) => {
      const { Books, Orders } = srv.entities
      srv.before('CREATE', Orders, async (req) => {
        const book = await{ ID: })
        if (book.stock < {
          req.reject(400, 'ORDER_EXCEEDS_STOCK', [, - book.stock])

    List of Generic Texts

    Find the current list of generic runtime texts:

    400=Bad Request
    404=Not Found
    405=Method Not Allowed
    406=Not Acceptable
    407=Proxy Authentication Required
    408=Request Timeout
    411=Length Required
    412=Precondition Failed
    413=Payload Too Large
    414=URI Too Long
    415=Unsupported Media Type
    416=Range Not Satisfiable
    417=Expectation Failed
    424=Failed Dependency
    428=Precondition Required
    429=Too Many Requests
    431=Request Header Fields Too Large
    451=Unavailable For Legal Reasons
    500=Internal Server Error
    501=The server does not support the functionality required to 
    fulfill the request
    502=Bad Gateway
    503=Service Unavailable
    504=Gateway Timeout
    MULTIPLE_ERRORS=Multiple errors occurred. See the details 
    for more information.

    Built-in Draft Support

    Class ApplicationService provides built-in support for Fiori Draft, which add these additional CRUD events:

    CRUD Operation Descriptiopn
    NEW <entity> To start a draft session with an empty entity
    EDIT <entity> To start a draft session on an existing entity
    PATCH <entity> To send changes during a draft session
    SAVE <entity> To finalize a draft session with applying changes
    CANCEL <entity> To abort a draft session

    You can add your validation logic in the before operation handler for the CREATE or UPDATE event (as in the case of nondraft implementations) or on the SAVE event (specific to drafts only):

    srv.after ('NEW','Books', ...)      // for newly created drafts
    srv.after ('EDIT','Books', ...)     // for starting edit draft sessions
    srv.before ('PATCH','Books', ...)   // for field-level validations during editing
    srv.before ('CREATE','Books', ...)  // run before create
    srv.before ('UPDATE','Books', ...)  // run before create
    srv.before ('SAVE','Books', ...)    // run at final save only

    These events get triggered during the draft edit session whenever the user tabs from one field to the next, and can be used to provide early feedback.

    More to Come…

    This documentation is not complete yet, or the APIs are not released for general availability. There’s more to come in this place in upcoming releases.