Create a Customer Detail Page in an MDK App

This page will show related details for a customer. In this page, you will add an Object Header control that is used to display information (like first name, last name, date of birth, email address & phone number) about the header of an object and Static Key Value control to display key value pair items like address, city, postal code & country.

You can find more details about available controls in section page.

In SAP Web IDE project, Right click on the Pages folder | New MDK Page | Section Page | Next.

You can find more details about section page.

Enter the Page Name CustomerDetail and click Next and the Finish on the Confirmation step.

In the Properties pane set the Caption to Customer Detail.

Next, you will add an Object Header container to display information like first name, last name, date of birth, email address & phone number.

In the Layout Editor, expand the Controls | Container section, drag and drop the Object Header control onto the page area.

Now, you will replace the default values of the control’s properties with the values from customer entity.

In the Properties pane, click the link icon to open the Object Browser for the HeadlineText property.

Double click on the LastName property of the Customer entity to set it as the binding expression and click OK.

Repeat the above steps binding below Properties:

Make sure to select values for the mentioned properties only from Customer Entity. You may find similar values from other entities. For example,

As enough fields have been selected to be displayed on the detail page, SubStatus and Tags are not required for this tutorial. In a real use case, you may need these properties.

Remove the default value for SubStatus properties.

Also, delete items under Tags.

Page should look like below.

In the main area of the page, let’s display some other details like; address, city, postal code, county.

Drag and drop a Static Key Value container onto the page under the object header.

Expand the Container Item section of the Controls palette and drag and drop a Key Value Item onto the Static Key Value container on the page.

Repeat the process and drag three more Key Value Items onto the Static Key Value section so you have a total of four when you are done.

Select the upper left Key Value Item and set the KeyName to Address.

For this tutorial, you will set the value as a combined binding of house number and street.

You can find more details about Target Path.

Start with first part of the binding for Address property.

Click the link icon next to the Value field to display the Object Browser and change the Format to Binding Target Path.

Click the checkbox for Current Object and double click HouseNumber to set it as the first part of the binding.

Be careful not to select HouseNumber from Address (ESPM.Address), final expression should be as per above animation.

Now set second part of the binding.

The cursor will be at the end of binding in the Expression field. Add a space and then select Street and click Insert to Expression.

Click OK to set the binding.

Be careful not to double click on Street as that will replace the existing expression with just the Street property.

Street should be selected from Customer entity.

Select the upper right Key Value Item and set the KeyName to City.

Click the link icon to display the Object Browser. Change the format to Binding and double click the City property of the Customer entity to set it as the binding expression.

Click OK to set the binding.

Be careful not to select City from Customer.Address (ESPM.Address) collection, final expression should be as per above screenshot.

Repeat the process and set the lower left Key Value Item Key Name to Postal Code and bind the value to the Postal Code entity property.

Repeat the process and set the lower right Key Value Item Key Name to Country and bind the value to the Country entity property.

Be careful not to select Postal Code & City from Customer.Address (ESPM.Address) collection, final expression should be as per below screenshot.

Save your changes to the Customer Detail page.

Now, you will create a Navigation action that opens the Customer Detail page when called.

Right click on the Actions folder | New MDK Action | Navigation Action | Next.

Provide the below information:

Click Next and then Finish on the Confirmation step.

Go back to the Customer List page and set the OnPress event of the Contact Cell table. You will link the Contact Cell table to the ShowCustomerDetail action so that when an end-user selects a customer, the Customer Detail page will open. MDK automatically passes the selected customer to the detail page.

In CustomerList page, select the Contact Cell Table, click the link icon under the Events tab for the OnPress property to open the Object Browser.

Double Click on the ShowCustomerDetail action and click OK to set it as the OnPress Action.

Save the changes to the CustomerList page.

Deploy the updated application to your MDK client.

Right click on the MDK Application in the project explorer pane and select MDK Deploy and Activate, click Next and deploy to Mobile Services.

Make sure to select required Destination Name and Application Id as per your target environment (Neo or Cloud Foundry).

Re-launch the app on your device, you may asked to authenticate with passcode or Touch ID. You will see a Confirmation pop-up, click OK.

Click Customer List, you will navigate to Customer List page.

Click any record from the list, you will navigate to it’s detail page.

Re-launch the app on your device, you may asked to authenticate with passcode or Fingerprint. You will see a Confirmation pop-up, click OK.

Click CUSTOMER LIST, you will navigate to Customer List page.

Click any record from the list, you will navigate to it’s detail page.

Are you wondering how exactly MDK knew that clicking on a record in list page would display respective record in detail page?

The MDK sets the current object to the selected record when running the on press action on the list. The detail page then just needs to reference the correct properties assuming they are part of the object from the list page.