Data Binding

The UI usually uses data binding to bind UI controls to the model, which holds the application data, so that the controls are updated automatically whenever application data is changed.

• One Way - a binding from the model to the view; value changes in the model update all corresponding bindings and the view eg. OData model
• Two Way - a binding from the model to the view and from the view to the model; value changes in the model and in the view update all corresponding bindings and the view and model, respectively. eg. JSON/XML Model
• One Time - One-time binding means from model to view once. eg. Resource model

onInit: function() {

var sServiceUrl = "https://sapes1.sapdevcenter.com/sap/opu/odata/sap/ZCD204_EPM_DEMO_SRV");

var oModel = new sap.ui.model.odata.ODataModel(sServiceUrl, true, "user", "psw");

sap.ui.getCore().setModel(oModel);

}

Here ServiceURL is oData Service url that should provide XML with list of collection available in the service.

OData Tutorial

• Consuming Gateway OData Services
• sapui5--practise-using-service-from-odataorg
• building-a-crud-application-with-sapui5-using-odata-model
• how-to-create-frontend-in-ui5-that-will-consume-odata-service/
• same-origin-policy-issue - reverse-proxy-with-url-rewrite-v2-and-application-request-routing
• new-e2e-tutorial-gain-hands-on-developer-experience-with-sapui5-and-netweaver-gateway

Working Demo

• Multiple Data Model Linking