---
parser: v2
auto_validation: true
time: 25
tags: [ tutorial>intermediate, programming-tool>odata, programming-tool>sapui5, software-product>sap-build-work-zone--standard-edition, topic>user-interface, programming-tool>html5, topic>cloud, tutorial>free-tier ]
primary_tag: software-product>sap-fiori
author_name: Nico Schoenteich
author_profile: https://github.com/nicoschoenteich
slug: sapui5-fiori-cf-fiorify
canonical_url: https://developers.sap.com/tutorials/sapui5-fiori-cf-fiorify
---
# Add Smart Controls to the User Interface
Replace the current UI controls with more complex (smart) controls that fully leverage the OData protocol.
## Prerequisites
- You have previously [created an SAPUI5 application](cp-cf-sapui5-local) and selected `SAP Build Work Zone, standard edition` as the deployment target.
- You have also completed all other tutorial as part of the mission [Develop an App for SAP Build Work Zone, standard edition with Your Own Dev Tools](mission.sapui5-cf-launchpad).
## You will learn
- How to use smart controls like the SmartFilterBar, SmartList, or the ObjectPage.
- Why smart controls can save you much boilerplate code.
---
### Enrich the products page with smart controls
Smart controls are a specific category of SAPUI5 controls that have some special super powers - the most prominent being the tight integration with the OData protocol version 2. Smart controls read the metadata of bound OData services, which allows them to easily provide features such as filtering, value help, and many more. Read more about smart controls in the [documentation](https://sapui5.hana.ondemand.com/sdk/#/topic/64bde9a8879d4f418e2849f7285dd757).
> Smart controls only work with OData V2. For OData V4, the [SAP Fiori Elements Flexible Programming Model](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/overview/introduction) provides "building blocks" with similar functionality.
>
> Also, the "freestyle" approach shown in this tutorial is only recommended for use cases that require a lot of custom implementation. If your application fits one of the available [SAP Fiori elements floorplans](https://sapui5.hana.ondemand.com/sdk/#/topic/797c3239b2a9491fa137e4998fd76aa7), you should [think about using SAP Fiori elements](https://sapui5.hana.ondemand.com/sdk/#/topic/0a5377076f4e4ccba055a9072befadbd.html) rather than a freestyle approach. The application built as part of this tutorial should probably also be using SAP Fiori elements, for the purpose of education however, a freestyle approach is shown.
Replace the content of the `myui5app/webapp/view/Products.view.xml` file with the following code, which imports various smart control libraries and makes use of the `smartFilterBar` and `smartList`:
```XML
```
Your page should now display product names and contain a smart header with fully functional filter capabilities (give it a first test run if you like).
> Did you notice that the list items display the category names, even though the selected entity set [Products](https://services.odata.org/V2/Northwind/Northwind.svc/Products?$format=json) doesn't contain these values. It does that because the property `expandFields="Category"` was defined, which expands the `CategoryID` to a full, nested entity. There is nothing you need to do apart from defining the field names to expand. All magic happens behind the scenes in the OData protocol. Feel free to remove this property from the view to see how the displayed data changes.
### Use the smart filter bar
You've already learned about the cool expand-feature of OData in the previous step. In this step, you'll learn about the complex filter operations OData supports out-of-the-box. For this, click on the **Filters** button. A dialog pops up, and you'll be able to define filters on all properties of the displayed entities. Select the grouped view and define a filter for the following criteria:
* The `ProductID` shall be larger than 3.
* The `ProductID` shall also be less than 8.
* The name of the category should be `Beverages`.
Close the dialog by clicking **OK** and apply the filter by clicking **Go**.
### Navigate to the detail view
Click on item **Rhönbräu Klosterbier** to navigate to the detail view. You'll upgrade this simple view to a full [ObjectPage control](https://sapui5.hana.ondemand.com/#/api/sap.uxap.ObjectPageSubSection) in the next steps.
### Use an ObjectPage in the detail view
Replace the content of the current `myui5app/webapp/view/ProductDetail.view.xml` file with the following code:
```XML
```
> As of now, this page only consists of a header that leverages data binding to display data. Note that the control `attrState` uses a special type of binding - so-called [expression binding](https://sapui5.hana.ondemand.com/#/topic/daf6852a04b44d118963968a1239d2c0.html) to display "Yes" or "No" depending on the state of the boolean variable `discontinued`.
### Enrich the detail view controller
The header of the view also contains two buttons (`addToCart` and `markAsFav`). In the next sub-steps, you'll implement the event listeners for these buttons.
1. Replace the existing file header of `myui5app/webapp/controller/ProductDetail.controller.js` with the following code, which imports the `MessageToast` control:
```JavaScript
sap.ui.define([
"tutorial/products/controller/BaseController",
"sap/m/MessageToast"
], function (Controller, MessageToast) {
"use strict";
```
2. Add the following methods to the body of the controller file (after the `_onRouteMatched` method):
```JavaScript
addToCart: function (oEvent) {
MessageToast.show("Added to cart");
},
markAsFav: function (oEvent) {
const oButton = oEvent.getSource();
if (oButton.getIcon() === "sap-icon://unfavorite") {
oButton.setIcon("sap-icon://favorite");
MessageToast.show("Added to favorites");
return;
}
oButton.setIcon("sap-icon://unfavorite");
MessageToast.show("Removed from favorites");
},
```
3. **Mark the page as a favorite** via the button in the header of the page to make sure the event handlers work as expected.
> Note that the icon is not supposed to do anything apart from being a toggle button. There is no (useful) controller logic associated with it and it won't store the state in the data model.
### Add more content to the ObjectPage
The following snippet defines the content of the `ObjectPage`. It's mostly basic and repetitive code. Interesting sections are the usage of expression binding for the link control `linkWebsite`, property bindings to the navigation entities `Supplier` and `Category`, and the usage of a custom formatter for the image control `imageCategory`.
1. Replace the content of the current `myui5app/webapp/view/ProductDetail.view.xml` file with the following code:
```XML
```
### Populate the empty fields
You probably noticed empty fields that do not show any data yet. Most of the fields are empty because they are bound to properties of navigation entities like `Supplier`. The data is missing because you didn't specify that these entities should be expanded during the programmatic binding of the view.
1. Update the binding definition, to expand the suppliers and categories, in the `_onRouteMatched` method of the controller `myui5app/webapp/controller/ProductDetail.controller.js` with the following code:
```JavaScript [6-8]
_onRouteMatched: function (oEvent) {
const iProductId = oEvent.getParameter("arguments").productId;
const oView = this.getView();
oView.bindElement({
path: "/Products(" + iProductId + ")",
parameters: {
expand: "Supplier,Category"
},
events: {
dataRequested: function () {
oView.setBusy(true);
},
dataReceived: function () {
oView.setBusy(false);
}
}
});
},
```
2. Now the `picture` field should be the only empty one. The field is still empty, as you need to add a custom formatter to deal with a [quirk of the Northwind image encoding](https://blogs.sap.com/2017/02/08/displaying-images-in-sapui5-received-from-the-northwind-odata-service/). Add this formatter after the `markAsFav` method to complete the controller.
```JavaScript
trimSuperfluousBytes: function (sVal) { // background info https://blogs.sap.com/2017/02/08/displaying-images-in-sapui5-received-from-the-northwind-odata-service/
if (typeof sVal === "string") {
const sTrimmed = sVal.substring(104);
return "data:image/bmp;base64," + sTrimmed;
}
return sVal;
}
```
3. The view should now look like this:
---