Salvation after 5+ years and variety of technological marriages, ABAP RAP is here finally. Fiori and WebAPI development can take a deep breath. This post is about common and uncommon snippets for ABAP RAP. This post is updated on regular manner.
If you ever worked with SAP GUI, you know the strong built-in capability which validates user input format based on the underlying Domain settings (DOMA) embedded into the Data Elemenet behind the user input field. Everything is automatic, comes out-of-the box.
XML Views represent the layout much better than JS Views in UI5. By default, lists etc. load a restricted number of items through aggregation binding. You can extend this without programming within XML Views. It requires configuration of the binding with the length parameter. This will set the $top option in the underlying OData query.
You want to disable caching at the client side. For example the web browser of the end user will not store the server response data You collected and sent back in Your Data Provider class. After project generation in SEGW transaction, the DPC_EXT class is ready to implement the method redefinitions to build responses for the client(get_entity,get_entityset etc.).
You want to activate services in transaction SICF in mass, but not all of them at once in an SAP system, which is frankly unnecessary in any context (an unnecessary security issue for example). One context could be activating all endpoints related to Fiori applications and OData services in a quality system, which were activated and transported from the development system.