Your root view is missing a root control such as sap.m.AppAPI which: Writes a bunch of properties into the header of HTML document, e.g. the viewport meta tag, Writes height: 100% to all its parent elements.[src] Without a root control, the content will be displayed improperly. Hence, adding an <App> should be sufficient in your … Read more
There is a solution for you. There is a event called routeMatched when navigation is triggered every time. You can attach the event in the detail page. onInit : function () { this._oRouter = sap.ui.core.UIComponent.getRouterFor(this); this._oRouter.attachRouteMatched(this.handleRouteMatched, this); }, handleRouteMatched : function (evt) { //Check whether is the detail page is matched. if (evt.getParameter(“name”) !== “detail”) … Read more
UI5 doesn’t support binding for class in XML view directly as it’s not a valid property of ManagedObject. Nevertheless, there is a workaround by adding custom data: Add CustomData with the property writeToDom to your control. Use your expression binding there: <ControlXYZ class=”myControl”> <customData> <core:CustomData xmlns:core=”sap.ui.core” key=”green” value=”foo” writeToDom=”{= expression}” /> </customData> </ControlXYZ> Depending on … Read more
I just went through the code of ClientListBinding, unfortunately the property binding for Filter value is not supported. Please check the source code here. See function getFilterFunction, the filter value is get from your Filter definition oValue1 and oValue2, it does not parse any DataBinding path to get value from DataModel. /** * Provides a … Read more
Here is a minimal example of combining multiple filters using OData from Northwind: https://embed.plnkr.co/AoIZI4/. The complete list can be found here. When instantiating a filter, instead of path, operator, and value1, use the properties filters and and to combine multiple filters as shown in the Filter API reference. In our case, we define three filters: … Read more
Bind the collection of data to the <items> aggregation of table. Add a new entry to the model (instead of to the UI directly) when the user clicks on Add. Thanks to the aggregation binding, UI5 will create a new ColumnListItem for you and you did not break the MVC pattern. Here are some examples, … Read more
getBindingContext(sModelName?) Get the binding context of this object for the given model name. If the object does not have a binding context set on itself and has no own Model set, it will use the first binding context defined in its parent hierarchy. You have given name to the model (this.setModel(oModel, “myModel”)). Specify the model … Read more
Avoid setting models on the Core directly if you’re using Components. Components are meant to be independent and reusable parts and therefore will not inherit the Core models by default. Models should be set depending on your business case: Models declared in the app descriptor (manifest.json) section /sap.ui5/models will be set on the Component. They … Read more
Accessing controls inside a fragment depends on how your fragment was created in the first place. Here is a list of cases with respective API to use to get the control reference. Given: this as a reference to the current controller instance Fragment required from the module sap/ui/core/Fragment <MyControl id=”controlId”/> in the fragment definition API … Read more
There is no need for “hacky approaches” or custom formatters in case you simply want to display the time (or date) in a human readable form. UI5 comes with the concept data typesdoc which has the following advantages: Let UI5 format, parse, and even validate the value for you. Supports two-way data binding in contrast … Read more