Show TOC

Step 23: Custom FormattersLocate this document in the navigation structure

If we want to do a more complex logic for formatting properties of our data model, we can also write a custom formatting function. We will now add a localized status with a custom formatter, because the status in our data model is in a rather technical format.

Figure 1: A status is now displayed with a custom formatter

You can view and download all files in the Explored app in the Demo Kit under Walkthrough - Step 23.

webapp/model/formatter.js (New)
sap.ui.define([], function () {
	"use strict";
	return {
		statusText: function (sStatus) {
			var resourceBundle = this.getView().getModel("i18n").getResourceBundle();
			switch (sStatus) {
				case "A":
					return resourceBundle.getText("invoiceStatusA");
				case "B":
					return resourceBundle.getText("invoiceStatusB");
				case "C":
					return resourceBundle.getText("invoiceStatusC");
					return sStatus;

Our new formatter file is located in the model folder of the app, because formatters are working on data properties and format them for display on the UI. So far we did not have any model-related artifacts, except for the Invoices.json file, we will now add the folder webapp/model to our app. This time we do not extend from any base object but just return a JavaScript object with our formatter functions inside the sap.ui.define call.

As the JSDoc comment block in front of the function says, the function statusText gets the technical status from the data model as input parameter and returns a human-readable text that is read from the resourceBundle file.

], function (Controller, JSONModel, formatter) {
	"use strict";
	return Controller.extend("sap.ui.demo.wt.controller.InvoiceList", {
		formatter: formatter,
		onInit : function () {
			var oViewModel = new JSONModel({
				currency: "EUR"
			this.getView().setModel(oViewModel, "view");

To load our formatter functions, we have to add it to the InvoiceList.controller.js. In this controller, we first add a dependency to our custom formatter module. The controller simply stores the loaded formatter functions in the local property formatter to be able to access them in the view.

				title="{invoice>Quantity} x {invoice>ProductName}"
					parts: [{path: 'invoice>ExtendedPrice'}, {path: 'view>/currency'}],
					type: 'sap.ui.model.type.Currency',
					formatOptions: {
						showMeasure: false
				numberState="{=	${invoice>ExtendedPrice} > 50 ? 'Error' : 'Success' }">
					<ObjectStatus text="{
						path: 'invoice>Status',
						formatter: '.formatter.statusText'


We add a status using the firstStatus aggregation to our ObjectListItem that will display the status of our invoice. The custom formatter function is specified with the reserved property formatter of the binding syntax. A "." in front of the formatter name means that the function is looked up in the controller of the current view. There we defined a property formatter that holds our formatter functions, so we can access it by .formatter.statusText.

# App Descriptor
appTitle=Hello World
appDescription=A simple walkthrough app that explains the most important concepts of SAPUI5

# Hello Panel
showHelloButtonText=Say Hello
helloMsg=Hello {0}
helloPanelTitle=Hello World
openDialogButtonText=Say Hello With Dialog

# Invoice List
invoiceStatusB=In Progress

We add three new entries to the resource bundle that reflect our translated status texts. These texts are now displayed below the number attribute of the ObjectListItem dependent on the status of the invoice.

Next Step

Continue with Step 24: Filtering.