RAP Side Effects in a Nutshell
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 properties after every user input, as it simply doesn’t know anything about data changes on the draft tables.
Side Effects can help you with that!
Finally, there is a simple solution to communicate with the UI by just adding some elements to your behavior definition in the backend. “Communication with the UI” in this case means to tell it when to reload which properties to get updated and thus consistent data.
Check out the video on SAP Developers YouTube channel for a quick overview on Side Effects:
Find the complete documentation on Side Effects in the RAP guide: ABAP RESTful Application Programming Model – Side Effects
This feature is available for the following products:
- SAP BTP, ABAP environment as of 2302
- SAP S/4HANA Cloud as of 2302
- For the availability on SAP S/4HANA and SAP S/4HANA Cloud, private edition, see ABAP Platform Roadmap Information: ABAP Platform: Roadmap Information
Thanks for sharing this video.
I have to admit I found "sife effect" for this feature an absolutely misleading term. Side effect in my eyes are bugs. However here it could have been called dependency or something similar. It would have been less misleading.
At least if there is a bug for this feature we could call it a "side effect for side effects" 🙂
Agree, Side Effects sounds misleading, especially because it already has a meaning in the context of programming.