When building a portal, it's important to know that portals have a similar build process as model driven apps. Meaning you should set up your data structure in data Dataverse as well as any forms and views you will be using before you build your portal. Let's start with customizing our menu header. To change the pages that are displayed in our header, we can go to the pages icon. And if I click on the ellipses on the about us page, I can have options such as adding a child page, moving it up or down, making it a sub page or delete this page.

Let's now try adding a new page. I'll select the new page dropdown and select a fixed layout called page with title. I can rename this page to My Appointments and now I can add a few components. Selecting the components icon, you can see that I have a good amount of options here. I can add the layout components to divide my content into sections. I can also add text, images, iframes, forms, lists, breadcrumbs, and even integrate Power BI.

Let's try adding a list, once added, I can give it a name. I'll say My Appointments. For our Dataverse data table, I'll select appointment. For the view let's choose the My Appointments view. I now have the options to include a button to create a new record, view details, edit a record or delete a record. If I select create new record, I will also need to select the target type. I'll select web page so that the user will be taken to another webpage in my portal to create a new record. To do this though, I'll need to add a New Appointment page and put a form on it. This time I'll select blank page. Let's rename it to New Appointment, and now I'll add my form and connect it to the appointment table. I'll name it, New Appointment. Select the appointment table and select appointment for the form layout. I'll leave the mode set to insert since we're adding a new record.

Let's go back to our, My Appointments page. Now when creating a new record, I can see it go to our New Appointment page. And that's it. In the next lecture we'll go over identifying differences in portal behavior based on user authentication.