Displaying Record Details

By setting the Web Page for Details View lookup to a Web Page,  the details of a record listed in the grid can be viewed as readonly or edited depending on the configuration of the associated form/page.

This page, can be a completely custom page template, perhaps created with Liquid or perhaps using a custom server-side .aspx page. The most common scenario is probably to have the details page be a web page that either contains an Entity Form or Web Form.

The important thing to be aware of is that each record listed in the grid will have a hyperlink to the details page and the link will contain a named Query String parameter with the ID of the record. The name of the Query String parameter depends on the ID Query String Parameter Name specified on the Entity List. The final thing to note is that the targeted details web page must also be aware of the name of this Query String parameter in order to get the ID of the record that it needs to query and load it's data.

Example: http://portal.contoso.com/account-details/?id=4C7A2949-E0CE-4DEA-AEAD-17889D5E8E9E

Web Page for Details View

Using Entity Form to display details

To create an Entity Form please refer the instructions found on the Entity Form page.

The following are the important settings to be aware of for ensuring the record from the Entity List is loaded in the Entity Form.

The Record ID Query String Parameter Name on Entity Form must match the ID Query String Parameter Name on Entity List.

The Mode can be either Edit or ReadOnly depending on your needs.

Entity Form Record Source

Using Web Form to display details

To create an Web Form please refer the instructions found on the Web Form pages.

The following are the important settings to be aware of for ensuring the record from the Entity List is loaded in the Web Form.

The Primary Key Query String Parameter Name on Web Form Step must match the ID Query String Parameter Name on Entity List.

The Mode can be either Edit or ReadOnly depending on your needs.

Using a Details Page for Create

One can also utilize a custom page, Entity Form, or Web Form, in the same fashion for the "create" function.  This is an alternative to defining a Create Action on the form: you cannot define both a create action AND a custom page for Create, and Defining a custom action takes precedence.

If you assign a Web Page to the Create Lookup on the Entity List, and do not specify a Create Action using Configuration, then a create button will be rendered on the list which will link the user to the custom page you have designated for Create.