To make our list of invoices even more user-friendly, we sort it alphabetically instead of just showing the order from the data model. Additionally, we introduce groups and add the company that ships the products so that the data is easier to consume.
The list is now sorted and grouped by the shipping company
You can access the live preview by clicking on this link: 🔗 Live Preview of Step 24.
To download the solution for this step as a zip file, just choose the link here: 📥 Download Solution for Step 24.
We add a declarative sorter to the binding syntax of the list control. Therefore, we transform the simple binding syntax to the object notation, specify the path to the data, and now add an additional sorter property. In the path of the sorter, we specify that the invoice items should be sorted by Product Name, and OpenUI5 will take care of the rest.
<mvc:View
controllerName="ui5.walkthrough.controller.InvoiceList"
xmlns="sap.m"
xmlns:mvc="sap.ui.core.mvc">
<List
id="invoiceList"
class="sapUiResponsiveMargin"
width="auto"
items="{
path: 'invoice>/Invoices',
sorter: {
path: 'ProductName',
}
}" >
...
</mvc:View>By default, the sorting is ascending, but you could also add a property descending with the value true inside the sorter property to change the sorting order.
If we run the app now we can see a list of invoices sorted by the name of the products.
We modify the view and change the sorter so the path addresses to the ShipperName data field instead of ProductName. This groups the invoice items by the shipping company. In addition set the sorter attribute group to true.
As with the sorter, no further action is required. The list and the data binding features of OpenUI5 will do the trick to display group headers automatically and categorize the items in the groups.
<mvc:View
controllerName="ui5.walkthrough.controller.InvoiceList"
xmlns="sap.m"
xmlns:mvc="sap.ui.core.mvc">
<List
id="invoiceList"
class="sapUiResponsiveMargin"
width="auto"
items="{
path: 'invoice>/Invoices',
sorter: {
path: 'ShipperName',
group: true
}
}" >
...We could define a custom group header factory if we wanted by setting the groupHeaderFactory property, but the result looks already fine.
Next: Step 25: Remote OData Service
Previous: Step 23: Remote OData Service
Related Information