Hi RAP developers,
I have extensibility news for you!
We have created a new video in which Daniel Wachs explains in brief what extensibility in the ABAP RESTful Application Programming Model is all about.
With its qualities of being natively inclu...
Hi RAP developers,
RAP business events are here! With this new solution for asynchronous communication, which is natively included into the RAP architecture, you can now trigger follow-up processes for significant changes in your RAP business object...
Hi RAP developers,
have you also struggled with data inconsistencies on the UI in your draft-enabled app? This can happen if UI inputs trigger data changes of other fields. The SAP FIori UI doesn't necessarily trigger a reload of all related BO prop...
With release 2105 of SAP BTP ABAP Environment, the ABAP RESTful Application Programming Model (RAP) evolves further. It contains numerous enhancements to make your RAP implementation consistent, user-friendly, and compatible with further RAP features...
With release 2008 of SAP BTP ABAP Environment, SAP releases stricter business object (BO) contract checks for the ABAP RESTful Application Programming Model (RAP) to help you make your RAP implementation consistent, user-friendly, and compatible to f...
Hi Cesar,
thanks for your comment! Please note that side effects are specifically designed for draft scenarios to get updated content on the UI.
Nevertheless, you are right. Currently, for CREATE and DELETE the side effect for a parent entity field...
Hi Jiangwei, this error message comes up if you do not maintain side effects in your projection behavior definition. Just like other behavior, side effects must be reused for consumption in the projection BDEF with the syntax use side effectsPlease ...
Hi Alejandro,
The sentence you are referring to was phrased a bit misleading. External Requests (OData calls) that are not contract-conform do not necessarily lead to short dumps. Instead, the stricter checks on consumer side (EML calls) enable dire...