1. 25. Create model-driven apps
Hello. And in this section, we say goodbye to creating canvas apps and hello to our model-driven apps. So, in canvas apps, we focused on individual controls and making sure we could place them exactly where we wanted, in pixels. In model-driven apps, we take a step back and look at the model. So we look at a site map; we look at forms; we look at views; that sort of thing. Now, let’s just create a model-driven application just from one of the demos. And to do this, I’m going to go into Create. and you can see all of these different templates. And there are a plethora of canvas app templates available here. I’m just going to create a model-driven app from one of the very few examples that they’ve got. So I’m going to use the fundraiser just so we can talk about what makes up a model-driven app. So here we can see that this model-driven app has been created.
It has a site map, forms, views, charts, and dashboards. It can also have business process flaws as well. And in the next section, we will be looking at business rules, business process flaws, and classic workflow. But in this section, we’re going to have a look at sitemaps, dashboards, and all of these entity views, forms, views, charts, and dashboards. So the sitemap you can see here shows that we have a fundraiser. We have dashboards, fundraisers, and donations. So I will just go back to the app designer, and I’m just going to save and close this and go into my apps. Here is our app, and I’m just going to now play it. So we just get an idea of what this model-driven app can do. So we have on the left-hand side all of those things that we’re looking at in our site map. And then we’ve got various views that we can filter on; we can show visual filters; we’ve got charts; all of this is in a dashboard. And we can go to other sections as well. So here we have a view that we can click on and go to various things, including forms.
As you can see, we can include video links and other elements. So this is what model-driven apps are all about. They’re all about combining views, forms, and charts into dashboards. And then you can go to individual items, click on them, maybe edit them, delete them, and that sort of thing. So while previously we were trying to get everything just right into pixel-perfect definition, here, this is more responsive. We’re looking at the model, so we’re looking at the data verse. So we’re modelling business data in the database. We’ve already done this. We’ve looked at tables, columns, relationships, and choice columns. You can also add security, including national, state, and local data regulations and company and trade regulations. But we’ll be looking at security in a later section. So to understand the model-driven app, we don’t actually need to look much at the model-driven app itself. What we need to do is have a look at the individual components, and we’re going to start that in the next video by looking at the site map or navigation.
2. 26. Create a site map
In this video, we’re going to have a look at creating our own model-driven app and the site map. So in the PowerApps portal, make powerapps.com. based on———based on——-based on—–based on the So we’ve got the classic app designer and the modern app designer. Preview. So, for this particular course, for this particular certification, the emphasis is currently on the traditional app designer. So I’m going to click Create, and that gets us to the page that we have previously seen. So first of all, we need to give it a name. So this is going to be accounts and expenses.
You can see you can use an existing solution to create an app. That solution is a collection of things like views, reports, and charts. But we’ll be getting into solutions later on. in this course. You can create a welcome page, and you can enable Mobile Offline. If you choose not to use the default image, then you can select your own image from this drop-down menu. So I’ve created the name; it’s a unique name. So let’s just click “Done” at the top. And you can also say “use the default image” if you want to. And now we get into our app designer, and the first thing you can see is that the site map is missing its configuration. So we’ll click on the pencil next to it, and that gets us into the site map designer. So we have areas, groups, and sub areas.So what are these? Well, let’s go back to our previous application that we’re looking at. This is a group. So a group is just a word in bold. The areas are the things you can actually click on to get to other places. The subareas are the things you can actually click on underneath the group areas. Well, there would be a little drop-down box here where you could switch to a completely new area. As an example, imagine areas as completely separate pages within your app.
So within each page, you have these subareas with group headings separating them. So let’s have a look at this. First of all, I’m going to click on the new area. So this title is going to be “Accounts.” So I can select an icon if I wish. I’m just choosing a random icon here, and you’ve got an ID here. So this is how things work internally. So I’m going to call this the Accounts area, and you have the option to show groups or not. Now within Advanced, if you are creating this for different locales, say Spanish for instance, you can change what the titles are. So maybe I wanted to create a Spanish name for this, and I will put, for example, “the account of Cuentas.” Similarly, I can add additional locales as I wish. So you can add multiple titles and multiple descriptions, and if you have Dynamics 365, you can enter the URL to render for the Dynamics 365 for Outlook folder that represents the area.
To be honest, you won’t have to worry about any of this most of the time. So it’s just the title that you really need to concern yourself with. Next, we have a group. So I’m just going to refer to this group as So this is just a heading, and as you can see, we’ve got the same things as well. Again, there’s one more option down here. This is advanced. You can select this checkbox to indicate that this group represents an easily selectable profile for the workplace. Again, you don’t need to worry about that. And then we have the areas. This is the main bit. This is really where you configure your app. And as you can see, there are four different types. So there’s a dashboard, so you can choose the default dashboard, a table or entity, so you can choose the relevant database table, a web resource, such as YouTube, and a URL, so you can enter a web page and any parameters passing to the URL. So we’ll go over dashboards later. Well, let’s say I want the account entity to be there. So I’m going to call this account now; I will add additional things to it later, but let’s add a new area just to show that areas exist and how they are represented.
And I’m going to call this the expenses, and within that I’m going to add, so you can drag in groups and new subarachnes, but I find it much easier to just click on “add,” but make sure you select what you want to add first. So add a new group. So this is my group number two, for example, and then I’m going to click on group two and add a subarea. So I’m going to say that this is an expensive entity and just leave it at that. So now this is done. The wording of this sentence is a little different than the one used in the video. Save and close; we’ll exit the site map designer, which is where I’m using all of these areas, groups, and sub areas, and take me back to the app designer. So if I do that, save and close. The RD symbol next to the site map has been removed. It’s looking much better. We’ve also added two new entities to the entity view: the table, the account, and the expenses. So what I’m going to do now is save this and publish it. You can also validate it, which is very useful to see if there are any missing components.
And as you can see, there are two warnings that the accounts do not include a form of your navigator’s expense or our plate. And here we can see we have the two areas, accounts and expenses, and we can change between them. And when we do, you can see that the group and the subarea change as well. So this is how we can design our site map. It’s there for the end user to be able to navigate through all of the different forms, views, charts, and dashboards. Now, if you want to go back into the site map, you can do so by just clicking on the pencil icon there. Now, what we can do, for instance, with this subarea is I can drag it to a new area, so I can just hover over the area. And there we can see account information now in the expenses area. Additionally, you can also clone items. So I’m going to delete that. You can also cut, copy, and paste. So it’s not just subareas that you can clone; you can also clone entire areas or groups. So let’s do that, and let’s click on this group. Let’s clone it. As a result, we can see the groups travelling side by side. So you can easily see everything that’s underneath a particular group when you’re actually playing it. Then they’ll go down the left-hand side of the page. So this is how you can create your own site map for your model-driven app.
3. 18, 27. Different types of Dataverse table forms
In the previous video, we created a sitemap, and that allowed us to see that we’ve got these two different entities, account and expense, which I’ll reference in the site map. And you can see we’ve got forms, views, charts, and dashboards. And it says all of that right next to it. Continuing on, we created the expense table as sales in the data.
First, we didn’t create any forms, but you can see that the computer did, and these may or may not be the ones we want to use. At the moment, it’s giving me all of the forms, but I can say, actually, no, all I want is one particular form. Now, if we’re going to account, you can see that there are at least three different types of forms. In fact, there are four. First of all, we have the main form. This is the main interface for table data. Then we have the quick view form. So these are only used in related tables. So these two tables are related to each other. It can display additional information in the related form. Now, there is one thing that is needed for the quick view forms to be visible, and that is in the table itself. So in the expense table or the accounts table, you need a lookup field; otherwise, the quickview forms will not be visible. Then there are forms that can be created quickly. So this is when you’re creating a new row.
And then finally, there’s a card form. So this is a compact view. It’s good for mobile devices, it’s good for dashboards, and you can colour code them. Now, I can create a new form up here. Alternatively, I can go into the Power Apps portal, make PowerApps.com go to Data, and go into the table. So let’s say I want the expense report and go into forms here. So I’m going to create a new form in the app designer. But while we’re here in the table section of Data, I want to show you what happens when you click on the dot next to any particular table and go to Form Settings. So we have four separate items. First of all, you can apply security roles to a form so that people only have access to certain ones. Secondly, if you’ve got more than one form, then you can say, “Well, I want people to be able to use this form.” And you can see that they recommend only having one form per security role. So you can say, “Well, actually, for the quick view forms, I’ve got all of these different ones available.” I want it to be shown in this particular order. Now, not everybody will have access to a form. Maybe you have a security role, and you say that group A has access to this particular form, and group B has access to this particular form. What happens if you’re not in group A or group B? Well, this is when fallback forms are necessary.
So each table needs to have a designated fallback form to be used when you slip through the cracks when there’s no particular security role for a particular user. And then finally there is the form access checker, so you can say, “Okay, I have this role for this app.” What can be seen So all of these are available in the datatable section, most particularly security roles and form order, and every table needs to have a fallback form.
4. 18, 27. Create and configure Dataverse table forms
So let’s create a new form for the expense table. So make a new one, and you’ll notice that we have options like Main Form, Quick View, Quick Create, and so on. So let’s go for the main form. and here you can see it opening up in a separate window. So this is the main form; it’s the main interface for table data. So, just like with the Canvas apps, we have a tree view on the left-hand side, and you can click on any particular item and any item that it contained. Within items, we have the table columns, and you can see that it says at the top, “Show only unused table columns,” so those that haven’t already been used. So I’m going to add in the date of expense, and I’m just going to drag it in just like that, along with the description. Also, I believe the account, related account, and expense value. There we go. Now if I click on any one of these, you can see on the right-hand side things that we can do. So we can hide the label, which will make it disappear from view. So, for instance, maybe we don’t need to see the word “description.” We can hide it on the phone. So if you have a small amount of space, maybe you don’t need to be able to see everything.
Or we can just hide it. Oh, where is it? Now, if I go away from it, how can I unhide it? Well, I’d have to go into the tree view and go into description. and you can see this little symbol. It’s an eye with a line through it, showing that it is hidden. You can secure it. So “lock” means that I can’t do things like, for instance, delete it. So if I go to the trash, at the top, you can see locked form fields cannot be deleted, and I can make it read-only so we can’t actually edit it. Now, we can also add components as well. So we’ve got various components. We have got four main forms: one, two, or three column tabs. We’ve also got one, two, three, or four-column sections. So if I drag that into here, you can see we’ve got all of these different tabs and sections. So this is useful if you want different kinds of information to be shown in different places. So this is where you can start working out. Okay, how do I want the end-user experience to look like?If I go back to components, I can either click here or here. With the components, we’ve got custom controls such as star ratings and number input toggles, and we’ve also got related data such as the Canvas app.
So if you’ve got a Canvas app that you want to embed into your model-driven app, you can do that. Also, we’ve got a quick view card, a subgroup, which is a view of a related table. We’ve got timelines, and we’ve also got knowledge search, so timelines show an overview of the activities. Only one timeline is allowed for form and knowledge search. You can see that it allows you to look for knowledge articles. Just one note: Quick view forms and subgroups can’t be added to quick create forms, so they’re best added to main forms. Now if I go into the header, we’ve got something called a “header density,” so what this means is that if I put in some things maybe like the status and maybe the approval status, things like that that probably won’t come up, you can see how it is shown with the head identity; it is very tight together. This is how you would display if it wasn’t very close together. So that’s all we mean by the header density. If you’ve got too many fields shown in the header, there is a drop box, technically known as a fly out.It’s an arrow, and it shows additional information there.
Then you’ll be fine. So what I’m going to do now is I’m going to save it. You can also save it, so I’ll save it and then publish it. So each of these actions takes a few seconds, and you can see incidentally at the bottom left what I’m designing for. So at the moment I’m designing for a laptop or desktop, so you might want to change that to a mobile device or a phone, or it might just be completely responsive, and at the bottom you can also see you can show hidden fields. So, if I go into my section, was it the general section? And if I say that the date of expense is hidden, then I can show the hidden fields or hide them, and I can also zoom in and out as I wish to. I’ll reset the zoom. So let’s now close this, and in here we can now see that we have a main form. So let’s save this app and let’s publish it. We can validate it as well. If you so wish, go into expenses. So click on any of these items, and there we have our new form. It’s not there. However, there is a dropdown next to the word information. Remember, I said all forms in the app designer. So there are two main forms, and I can say, okay, actually, I want the main form. And here you can now see the main form with these two tabs: new tab and general. We also have related items for ancient history and background processes that are standard. And then if I want to edit any of these—let’s say I wanted to edit this—
I can go into the data and just edit it. So maybe I’m saying it’s the next day, and then I can save it or save and close it if I wanted a new one. So this is a new cost; clicking on it takes me to the same form, the same main forms. Except now I can create if I so wish. Now let’s just go back to the app designer. So I’m going to edit this main form because I want to point out that there is a classic form editor as well. Now, I don’t advise using the classic formulator unless you have something very specific. So you can also have a reference panel for the main forms. So that’s sort of like the related data. You can have spaces, and you can have Bing maps. So if I’m going to insert at the top, you can have Bing maps, you can have the timer control, you can have web resources, you can have custom controls, and you can have a few more things. So what they’ve tried to do, Microsoft, is create a more usable way of creating forms.
So this is called the “Unified Interface,” the standard way of creating it in both the classic and modern designs. However, they’ve not been able to incorporate everything into it just yet. So you can see that we’ve got these two different tabs, one above the other. We’ve got the header, then we’ve got the footer. It’s quite a different way of showing the design of your form. So these are forms—four different types of forms. main interface, quick view forms used in related tables, quick rate forms for creating new rows, and a card form, a compact form view. And then when you’ve got all your forms, To specify which order the forms should be in, go to form settings and create your security rows. So I can drag that up, for instance, and then a form will fall back form.If a particular security role doesn’t have a form selected, then you’ll have a fallback form, but only one per table.
5. Embed a canvas app on a form in a model-driven app – Unified Experience
In this video, we’re going to start looking at how we can embed a Canvas app on a form in a model-driven app. So we’ve got a Canvas app, and we want that in a model-driven app. Maybe we want it on a separate tab. So I’m going to show you how to do it in the unified interface. So that’s the modern interface that we’ve got. So I’m going to do this in the account table, and then I’ll go over to the forms. And we have the main form here, which I’ll edit in a new tab. So I’m going to create a new tab that is completely separate from everything else. So I’ll go to Component and add a one-column tab. So there’s our new tab. So I can click on the tab, and I’m going to call this app Canvas app.
Now what I’m going to do is go to the Plus button again and go to the Canvas app. Now we’ve had a brief look at this, but we’ve got all of these different things. So let’s take a look and see what we can do. First of all, we’ve got the entity name. So that’s the table. So this is the balance sheet. We have the app name or the app name that I want to do here. And I’ve just opened up a second tab so you can see everything. So it needs to be a Canvas app. and it will be the Accounts app. So just type in the Accounts app, and the app ID is next. And to get that, I click on the dot, go to details, and there is the app ID. So I’ll copy that Control and V, then cut and paste them. And after a second or so of scrolling down, you can see that Done is there. Control the component now using a mobile device or tablet. Now, please note, you can enable up to three embedded Canvas apps for each form on the web, but only one for mobile and tablet. Why is this so? Well, it takes a lot more processing power and a lot more communication to not just load a model-driven app but also a Canvas app on top of that.
So I’ll click Done, and you can see we have our Canvas app here. So looking at the components, I can click on the component over here and click Edit. So, if I need to change anything, I can also change the section and the Canvas app. The tab also expands the first component to the full tab. So I want the first component, in this case the Canvas app, to take up the entirety of the tab. So I’m just going to save this. I’m then going to publish it, which takes a few seconds. Okay, so now I’ll go back. I’m also going to publish it a second time, where I’m going to go to solutions and publish all customizations. So when I’ve done something big, I always like to make sure it’s certain. Sorry. And then I’m going to go into the apps. I’m going to edit our model-driven app to ensure that this app is there and this form is there.
So I’ll click on the form, and you can see everything is there. And there is the account form. That’s the main one. So I’m going to save this, publish it, and play it. So if I go to all accounts, I can see all accounts. I click on one of these, and you can see I’ve got a summary tab, a details tab, and a Canvas app tab. So this is the one that we have edited. I click on the Canvas app tab, and it doesn’t seem to do anything. So this is how you are meant to be able to add a Canvas app to a model-driven app using the unified experience. Except it doesn’t seem to work for me. So let’s go back in. You can clearly see something has worked because we got the tab, so it has actually been published.
So let’s go back to the tables. Let’s go back and take that into account. Return to form and open a new tab to edit this form. Now, if I go to the tree view, we can see the Canvas app, and there it is. So I’m just going to delete that. Okay, well, maybe I can delete the section. Maybe I can delete the Canvas app. It’s no longer showing here either. It’s not showing the actual app itself. And when I click on it, it’s not showing any width or height. So basically, I have not been able to get this to work. in the unified experience. It should work. And you can see I still have all of the things, but I can’t even delete them now. So in the next video, what we’re going to do is show you my preferred way of doing this. Most of the things that we’ve looked at—looking at the entity name and the app name and so forth—and the app ID are exactly the same, except we’re going to do something that actually seems to work.
6. Embed a canvas app on a form in a model-driven app – Classic Editor
So in the previous video, I tried to embed a Canvas app in here, in my form. But unfortunately something doesn’t seem to work, so I can’t even delete it now. So that’s why I switched to the classic. And here it actually does work while using exactly the same sort of data. So what I’m going to do first of all is delete what I previously wrote. So I’m going to scroll down, and you can see the canvas area. And here I can press delete, and it actually works. So I can delete the Canvas app. So what I’m going to do now is just double-click on the words “Canvas app,” and I’m going to call this Canvas app too, so you know that this is the new version. So what I’m going to do now is just drag in any old field. So I’m going to drag in, say, the account number, account rating, or just any old field that will go in there. So normally, you can see that this is going to be some sort of field that it would just display. I’m going to double-click on it and override it. So I don’t want to display the label on the form. So I’m going to go to Control with this account rating.
So it’s currently an option set. That’s the old name for option. So I’m going to go to Add Control, select a Canvas app, and click Add. Now, at the moment, the option set or choice will be used for the web, the phone, and the tablet. I’m going to change that. So the Canvas app will be used instead. So you can see that the entity name is “Account,” the app name. So this is when I look it up again, just to make sure I’m getting the exact wording of “Accounts app.” So go back in here. So I’ve clicked the Edit button, the Accounts app, and the ID. So get down to business. Is this here? So make sure you bind to a static value.
You can bind to a value on the field or in the unified experience of a column. Microsoft does not recommend you do that at this stage. So the advantage of that is that you could have a different Canvas app for a different role. So some rows could go to one Canvas app, and some could go to another. So there we go. Click. OK, so I’m going to save this, and I’m then going to publish it. So notice this is called Canvas App Two, so we know we’ve got the right thing. So I’m just going to close most things and go back to solutions and publish customizations just to make sure everything’s fine. And then I’m going to do exactly the same thing that I did before. So I’m going to go to my model-driven app, edit it, and make sure that the form is selected. So there’s the form, saving, publishing, and then playing. So again, I’ll go to all accounts to see a list, click on one of them, and now we can see we’ve got the Canvas app too.
So this is definitely the updated version. I click on that, and there you can see our Canvas app. So I can go click “view accounts,” and there we have it. If I resize it a fair bit downwards We can actually see it at a normal size. You can see that it works exactly as it should. So this is a preferred way of getting a Canvas app into a model-driven app. Now, I have to say, it’s not totally my favourite way. This way works, but it doesn’t actually have anything to do with what we are adding or what we are editing. So in the next video, what we’re going to do is create a Canvas app from scratch, but we’re going to do it in a different place than where we’ve done it before.
7. Embed a newly-created canvas app on a form in a model-driven app
So in the previous video, we embedded a Canvas app into a model-driven app. But it doesn’t relate to this specific entry that we were looking at. So how can we change that? Right, well, let’s go back to our form. So go back into tables, back into accounts, back into forms, edit the current form, and then go right back into the classic experience for the form. So what I’m going to do now is, again, just delete what was, and then I’m going to call this a different number. As you can see, it can be difficult to decide whether to click on these things that collapse or not. As a result, this will be a free app. So again, I’m going to drag a field into this area. Again, I’m going to hide the label. I’m going to go back to Controls and add Control and the Canvas app.
So far, everything we’ve done is exactly the same as before. And again, I want this to be displayed on the web form and tablet. If you don’t do that, you’ll just get the choice—or option set, as it used to be called. But now I’m going to do something different. I’m not going to add an app name. I’m not going to add an app ID. Instead, I’m going to click “customize.” So you can select customise to create or edit your Canvas app in Powerap Studio. So I’m going to start with a completely blank Canvas Power app. So this is a completely different way of creating our app and a completely different way of starting it. So this is going to be a very simple one. And I want you to have a look at what is here. So what we have is a form. Inside the form, we have some cards. So all of these have been automatically added. I’ve not done any of this. Now let’s have a look at the form, and then let’s go to advanced and items. And you can see that going this way, there is a special value. We’ve got model-driven form integration.
So what this is is the model-driven app referring to the Canvas app; this is the data for the record that we are currently on, and the item that it’s currently looking at is the current item. Now, there are a few things you can do with this. For example, we can say “dot data” and then “dot other things” or “dot an item.” And if we want to get to a particular field, we can go down there. But if we want a record, then that record is a model-driven form integration item. So you might find this created for you, if not simple to do. We just go to insert forms, edit, and the data source is the accounts data, and the item is the model-driven form integration item. So there you have it. So if you do need to restart it, That’s how you do it. And then we can add fields as you wish. So maybe I will add a bigger version of “Address One,” say, the state or province. There we go. Now, just one more thing. If you remember when we were talking about Canvas amplifiers, we had these icons: the check icon and the X icon. And it’s only when you click on the check icon that anything is saved. So it doesn’t mean that if I make any changes to this, they’ll be saved. So I’m going to resize the form. I’m going to insert a button. So this button will be Save Changes.
And the changes were brought about by what was entered into the OnSelecttoSave box. It is a submission form. So that actually saves the changes. Make sure it’s below the actual form. If you have it too high, you might not be able to see it. So there are my saved changes. So what I’m going to do now is save this. I’m going to publish it and then close this. You can see the app name and appID have been filled in by the computer. I have not had to do that. If I want to continue editing my Canvas app, I can just click on Customize, and that loads the Canvas app for me. If I want to return to it, I can double-click on my field and then select Controls. So I click “Save,” then “Publish,” and now I can close this. I’ll also close this form as well. So I’m back to the menu. I’ll go to Solutions and publish all customizations. I’ll then go into Apps and open my model-driven app. And there is my Accounts & Expenses app.
So I will edit it, make sure that all the forms are selected, click Save, publish, and then play. So select an account. Notice that we’ve now got canvas. App three. Just reduce the size a bit. So there we go. And there we can see the form with Save Changes. So I’m going to change this address from Santa Cruz to Santa Cruz Two. and click on Save Changes. Right? So if I go to the summary tab, will I see Santa Cruz or Santa Cruz too? and I’ll still see Santa Cruz. So you’re going, what? Is all of this time spent watching the last three videos a waste? Can’t I change what I want in my model-driven app using a Canvas app? The answer is yes, you can. If I show you, I will now go back, and you can see that Adventure Works is now in Santa Cruz Two. And when I go back into it, you can see Santa Cruz Two here. But why didn’t it happen when I just clicked on the Canvas app? It’s because this model-driven form doesn’t have what’s called an event handler. It doesn’t know that things have changed. So it’s not going to query the data.
So I’ll change this back to Santa Cruz. Click save. It still says Santa Cruz, too, because that was the information it got when it loaded the form. But if I go back, you can see we’re in Santa Cruz, and if I open it again, it says Santa Cruz. So all this means is that the Canvas app doesn’t really talk completely to the model-driven app. But any changes you make in the Canvasapp will be saved to the original data if you do something like submit a form. So in this video and the previous videos, we’ve seen how to embed a Canvas app on a form in a model-driven app. So it’s meant to be fairly easy to use the unified experience. All you do is go to components and add it. But for me, it doesn’t work. It may work for you, but it doesn’t work for me. So if it doesn’t work for you, and to be honest, I prefer using the classic version for this in any case, because I can then connect my app to the data that it came from. Then I switched to classic. I drag in a field, and within that field, I generally hide the label, and I go to controls and add a control. I add a Canvas app control, and then I click on Customize to create a new Canvas app, which can then be embedded in my model-driven app.
8. Practice Activity Number 9 – The Solution
So how did you find this practise activity? So we’re starting to look at model-driven apps in this section. So I’m going to create a model-driven app from scratch using the classic App Designer. So click “create.” So I’m going to give it a name. So this will be the user and device model, and everything else is fine. Go to “done.” And now it takes me to the app designer.
configuration is missing. So I’ll click on the little pencil mark. So I want this first area to be regarding users. So let’s type in “Users” and the subgroup. Again, I will just call it “users” and the “subarea.” So this is the real thing. It is going to relate to a table and an entity. So the entity is going to be the user entity. And again, I’ll just call these users. So we will have at the bottom left of the screen an area with a drop-down list saying “Users.” And then we will have a bold heading for users and a less bold heading, a normal heading for my user. So I’ll call it the “users” subarea. So next, I’m going to add a new area. So a completely new section So this is going to appear at the bottom left of the screen. So this I will call “devices” and add to a group. Notice I couldn’t add in a subarea at this stage. It’s got to have a group. And then within that, I’ll have a sub area.And this will be the entity for devices.
Simply save and close the “devices” subarea. So that will exit the site map designer, and we’ll go into the app designer. Now notice that it has now created two items. Here in the entity view, we have devices, and we’ve got forms. And also notice that we have some forms and some views. No charts and no dashboards exist for our new table that we’ve created. So let’s create a new form. So click “create a new main form.” So this opens up a new window. So I’ll just maximise this and zoom in a bit. So I want to add to this device’s name. So let’s go into the table columns. So device name. Just drag it in there and type “device” now in a new one-column section. So that’s a component. So we’ll add that in. We will then have a date purchased. So drag that in. So I want to name the section. So we’ll call that date and then create a new one-column tab. So let’s drag that in. So there’s our new tab. We will have device status, the original purchase value, and the current value. There it is. And we’ll rename this section OverDetails and this tab Over. Now remove honour from the form. So let’s start with the broad strokes. We’ve got things in order here.
So I’ll just press delete and notice it doesn’t work. Required form fields cannot be deleted. So we’ll have to hide it instead, and then make sure that device name is right at the very top. So we’ll just drag it up. So that is our new form. So we’re going to go to Save. You can see that you can also save it as So I’m going to save that. So if you want to name it, then Saveas is probably better, and then we’ll publish it. Notice, incidentally, at the bottom, you’ve got a show hidden. So if you wanted to see the owner, you can do so now that it’s published. You can see there that we have our main form. Aftermarket Placementi Click here. You can also validate it as well, just to see if you’re missing anything. And you can see there are two warnings, and those warnings are for approx. Users will see all forms and all views. That’s fine. And then we’ll play with it and test it. So we can see we have users. So we have got the user area here, the group here, and the sub area here. When I click two devices, we get Devices and the Devices subarea. And then if I click on one of these, I get to our form that we’ve just created. So here we have the general tab. Here we have the other, and then we have a few things that are added to most forms. There we have the related. So in this section, we’ve had a look at model-driven site maps and forms. In the next section, we’re going to have a look at views. Please join me there.