MS CRM Portal : Web Page Configuration

Web Page is use to display the content of website. It represents URL in Portal. It is represented with logical name adx_webpage.

In development of Portal, we can create Entity List (Display the records in table), Entity Form (Display entity form view layout) and Web Form (To display the HTML Page). All these components are consumed by Web Page. So Web page is kind of gateway to view the contents of Portal.

In Portal development we can think Dynamics 365 basically as Database and MS Portal provides extensibility to design the Front End and Middle Tier of website type design. 

While designing the front end we use the combination of Web Template, Page Template and Web Page. The Web Page uses the other component like Entity Form, Entity List etc. from D365 entities to extends the D365 features.

The middle tier can be design as coding part of Web Template, Web file etc. On the web template we code Liquid Scripts to fetch data form D365 Database. The output logic from code will be viewed on Web Pages.

Web Page can have Parent and Child Web Page hierarchy like under Home page we can have another child page. (Home - > Child Page). It is also the basis of other portal entities such as blogs, forum, shortcuts and web files.

Create New Web Page:

Name : Enter the name of the web page.

Website: Select the web site for which web page is being created.

Parent Page: Select another web page under which this web page should be displaying. Example: I am creating web page with partial URL 'create-application' and parent page is Home page then web page URL will be formed as below.

Partial URL : Enter the partial URL by which this web page will be retrieved.

Page Template: Select the Page Template under which if any coding can be updated. Page Template will have parent Web Template where liquid script or custom code will be placed.

Advance Form: If we want to display and any advance form (forms with the steps in web page) then select the Advance form.

List: If we want to display the any Entity List or List of records in table form then we configure the entity and that entity we need to select on the web page.

Basic Form: If we want to display the layout of fields from Entity D364 forms then we configure the Basic Form (Entity Form) and that form we need to select in the web page.

These are the important field which need to be filled while creating new Web Page. There are some fields too it can field based on details provided.

An Example of Web Page configuration is as below:

Web Page consist of two form type. 

• Information 
• Localized Content

Information Form Web Page will be kind of root page. There is one Boolean field with name like 'Is Root'. It will be marked as Yes(True) to indicate the page is Information page and if it No(False) which means the page is Content page.

Localized Content page is actual Web Page which will be loaded on Portal website. So if Portal is configure for only English language then one English Language content web page will be automatically created. 

If we have portal configured with multi-language supported then we need to create the Localized Contend web page of each language (Language enabled in Portal). 

If portal is not configured the Localized Content web page then when we navigate the Portal with another language (for which localized content page is not created) then nothing will be loaded since localized content page will not be found to display the contents or information.

So it is important to check the Localized Contend page for each language enabled in Portal.

Configuration of Localized Contend page is similar to Information page but we can set the Language of Content page, Title (It is kind of page header). If we have any custom HTML, CSS, JS code those can be placed in code area (Designer/HTML).

There are some other main configuration which can be enabled on Web Page for more user interactive feature like Rating option, Search options etc.