I wanted to build an app using CAP that has transactional capabilities. Since the app is completely based on a remote service, I need to have custom handler logic to handle CRUD operations. In cap, in order to enable create/update, the entity needs to be annotated with draft enabled. We don't need draft because we are not persisting the data and the entity is already annotated with persistence skip whenever we create the entity as a projection on remote service.
Is there a way to perform create/update in a CAP app by disabling the draft functionality. I tried the annotation @odata_draft_bypass and it does not work.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.