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.
Save time and have much clearer coding instead of implementing specialized confirmation Dialogs in Fiori / SAPUI5.
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 […]
You want to activate services in transaction SICF in mass, but not all of them at once in an SAP system, what 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 […]
for Freestyle Apps and manual SEGW service implementation Fiori applications can retrieve texts and translations both from the backend system and from i18n resource bundle files of the application. However might happen, that these changes do not become immediately active, when users relaunch the applicaion.
You want to gain capabilities of SAPUI5 Smart Table control using a GateWay service. Nice control, but at the moment with limited availibility of documentation and examples. Two points can make you headache. You want to bind to backend entity set, which is not directly accessible, but it is an associated entity, and you can access it […]
When you want to save some variables at the client side, without using an OData Model connected to the backend, you can do it using a model of type JSON in your controller. Like you define objects using JSON, you can have a nested hierarchy. It’s possible to set defaults of any type, and reference […]
SAP is focusing development of sap.m library instead of sap.ui.commons (discontinued). It is obsolete for us during development. They officially state that combining these libraries is not possible, which is other reason not to use this library. The below figure shows you, what can be combined, and what is not safe. As you can see sap.ui.commons and sap.ui.ux3 are […]