2.1 Modeling the results list

We will start with tailoring result columns in the search view by updating the output parameters of the "read list" operation on the "sales order" object. This is where we need to take a look at the output parameters, and decide which ones we want to remove, which ones we want to add, what is the order we want them to go in, and which parameters may need to use a different type from the type of the corresponding field on the object, so that they could be displayed differently on the screen.

The picture below shows parameters that we decided to remove in red boxes on the left, and the final structure of the output on the right, with the parameters that we want to keep, and their order within the output structure.

The dates on the sales order, such as the order date or the ship date, are stored as date/time in the database, and hence their fields are defined like that on the object as well. But it makes more sense to display them as just dates, without the time component, so we went ahead and overrode their type on the output parameters to be just “date”.

Also, in the AdventureWorks schema, the customer is a business entity that may be either an individual person or a store, which could also have a contact person. To display that properly on the sales order list, we will show it as two separate fields: customer store and customer name. Since neither of them matches a specific field on the object, we will need to qualify them with a logical type (e.g. string).

Also note the "config" section of the output structure, which specifies that all these result parameters should be added as properties to the client data object SalesOrderList, which is defined separately in the model. This data object serves as part of the view model for our search view, and we will be updating it to further adjust certain UI behavior.

Next: 2.2 Adjusting fields’ visibility and labels, configuring links’ display >