Certified Advanced Administrator Certification Video Training Course

Certified Advanced Administrator certification video training course by prepaway along with practice test questions and answers, study guide and exam dumps provides the ultimate training package to help you pass.

Extending Custom Objects and Applications

5. Leveraging a Junction Object Across Multiple Record Types

I want to make sure that you have access to both record types for the Asset object. So I'm in the system administrator profile. So just go to Profiles, set them up, and select System Administrator and then Object Settings. And then I selected assets. And so it's here that I see that I've got the medical equipment record type assigned, but not office equipment.

Now show the implications of that before I assign the office equipment record type as well. So if I go into Assets, which you can get to by clicking on the App Launcher and just selecting Assets from the All Items list, if I go to create a new asset, it doesn't give me the option to select a record type. And so that means that I need to assign that other record type to my profile. So if I click edit, I will also assign office equipment to myself. And I believe I'll make office equipment by default.

I'll click "Save." Alright, so now if I go back into Assets and select "New," I actually need to refresh the screen in order to hit the server again. So that the "New" button will pick up on the fact that there are two record types available in my profile. Now, I need to select the record type of either office equipment or medical equipment. And you know, it's the default that is selected for me on my profile: office Office Equipment. And so I'm going to go ahead and create a new asset record for office equipment. And we're just going to call this a desk. And here you can assign these to different accounts, contacts, and products via these lookups that we noted previously. These are the lookups that are on the asset object by default in Salesforce.

So I'm just selecting an account and then a product. So you can just search for "genuine." This is actually a diesel generator, not the best product designation for a desk. Let me do a new product to tie it to this desk. So I probably shouldn't say this, but back in the day, man, this could get me in trouble, but oh well. All right. So probably 20 years ago, yeah, about 2022 years ago, I had occasion to go to the corporate headquarters for Walmart, and they had a row of people working at desks that were nothing more than saw horses and plywood.

So draw your own conclusions from that. All right, so I'm creating a product and making it active. And we won't put it in the non-product family, as opposed to the non-product family. Sometimes it's a little thing that strikes me as odd inside the Salesforce product code. I'm just going to put "Gibberish Here," "Product Description," and "Save." So then, a lot of times in companies, they'll number different items, even office equipment, so you can keep track of specific units or items. So we'll just say that this actually has a serial number on it as well. And then you can also enter quantity and price information.

If a large number of desks are being installed, for example, you can tie the price to the product or asset and even track the purchase date. We're just going to click "Save." So now I've got an asset, and it's a desk that's tied to the saw horses and plywood products. Now I could add a contact as well. Let me see who I've got in the gym's account for a contact, and it's here. There are no contacts. So here's where a use case, for example, of having a search filter on contacts would make it so that only people who belong to this account could be put on this asset. For example, I'm just going to tie this asset to Edna Frank with Gene points. It's a different company. So I'm just going to save it. The main point here is just to get a record in place.

And so now that we've got this asset associated with an account, a contact, and a product, let's look at those records. And I believe we'll have to add the related lists for assets onto those page layouts. So, when we go into the gym's account and click "Related," we don't see the asset-related list for contact, and we don't see the Frank no asset-related list. And then for the product as well, going to the related tab, there's no related list for assets.

And so I'm not so concerned with the product object, but for accounts and especially for contacts, especially office equipment, I think it'd be helpful to have a related list to be able to assign assets to a contact record directly from the contact record through a related list. So we are on the contact list. So if I go up here to this gearicon and select "edit object," that takes me to the object manager for the object that I'm on.

So, for the contact object page layouts, it would be nice to have some sort of hint as to which of these page layouts is assigned to my profile, or to have the force.com fly-out menu as you do in Classic whenever you're just on a record itself. But, thanks to Lightning, you'll have to dig a little deeper this time. All right, so if we go into the contact layout and I see "system administrator," this is the page layout that I have assigned to myself. And you'll notice that the assets related list isn't on the page layout here under related lists. So I can click and drag this down into the related lists section and drop it, and then save the page layout.

And then, if I go back into the contact record, let me refresh this. and we should see the related list. And so now we have the asset-related list. We have a desk that's been assigned to her. All right, so we've added the related list of assets to the contact page layout.

You could do the same for accounts. You could also do the same for products if you'd like. For now, I'm just going to make this available on the contact record. And from here, you can create additional assets, and those would automatically be associated with Edna Frank. For example, if I wanted to create an X-ray machine as medical equipment and associate it with the actual account that this contact belongs to, And I'm not going to tie it to a specific product, but I'll enter a serial number.

I'll leave the rest alone. Just click "save." So now we have an example of a medical equipment asset as well. So there's something else you might want to do. We have assigned office equipment. This desk is made out of sawhorses and plywood. And we've assigned that to this contact of Enda Frank, and we've assigned it to an account that is not the one that Edna is in, which is Jim's account.

As I mentioned You may want to do search filters to limit some of that, or you could do validation rules. as well, now that I think about it. But the main point is that we want to focus more. If we refer back to my work of art, what we've dealt with so far is that we added a related list on contact to be able to add assets.

And you could do the same by changing the page to allow for account and product creation to allow for the creation of assets from the product or account detail page and creating the asset and associating it with whatever records are on there. And then, previously, we did make sure that both record types were available in our profile. And so now, with this X-ray machine that I just created, I want to assign it to a room. So let's see if we can do that and, if not, what we need to create in order to make that happen. So we've got a custom object of room and a junction object of room assignment. So as I return back to my desk, if we go to the related list here, we see that there's no relay list for either room or room assignment.

So let's go and edit the asset object, and then let's go into its page layout. And I'm not going to edit the page. I need to get to the underlying page layout, not the lightning page that encompasses all that you see here on the screen. So we're in the asset object and object manager if we go into page layouts, and if we look at page layout assignments, we just have the one page layout, if I recall, across the various record types. We have medical equipment and office equipment, and the master record type is across all profiles. So it makes it kind of easy in this instance because we just have the one-page layout at this point. So I'm going to click on Asset Layout. Let's look at related lists. So, here we have the Room Assignments Related list.

This is our Junction object, and we want to bring this into the user interface so that we can assign these assets to a room, for example. As a result, you can place this anywhere in the Related List section. I'm going to put it toward the top, and you can also adjust to allow for other columns in the related lists here. As you can see, we have room assignments as well as room fills. These are the available fields to show in this related list. So these are the room assignment junction object fields that are available, and these are the room custom object fields that are available.

And my display is too large; there is a button for "New," and I need to be able to resize this. So let's pause for a second and let me resize my display. All right, so hopefully we can make out the smaller text. Now before I click OK to save what I have so far, let me click the plus sign on the buttons section here. And I wanted to make sure that I had the new button selected so that we could create a new assignment from the asset record.

There is also a ChangeOwner button available. So I'm going to leave that in place and click okay. Now we have our related room assignment list. If I click Save and click Yes, let me pause once again, and then we will look at this from the user interface, So, let's go back to our asset, our desk, and refresh the screen, and we're on the Related tab, where we may need to return. And now we have our room assignments. Now bear in mind that we haven't created any rooms yet. Let's see if we can do that, as we're doing a room assignment. So, if we click New, a window for searching for a room will open. We've not created any yet, so we're going to create a new room. And so let's click save.

And so now we have our asset assigned to a room through the junction object of a room assignment, which we did through the new button thanks to the Related list. Now, as well, we should be able to assign medical equipment if we go back to our diagram. We just assigned a piece of office equipment, our desk, through a room assignment to a room called Conference Room A. So now let's go through the process of assigning medical equipment.

So, if we go to our assets, we'll be returning to salesforce. If you recall, I also made an X-ray machine in this lesson, but it was of the record type of medical equipment. So, if we look at the Related list, Here we have the same related list because we have the same page layout, in essence, on the asset object, regardless of record type. We could change page layouts by record type and have different page layouts. But for now, we just have one. So I'm going to click "new." And now we can assign this x-ray machine, which has a different record type, to a room of our choosing.

And you'll notice that we have this one room that we created, conference room A. And I've already forgotten what this icon is, but it is that medical-looking symbol. So now for this X-ray machine, let's say that we're putting it in surgical recovery room B. Let's click save. I'm looking for something to use as a new room name. I'm getting a little ahead of myself. So click "New Room" and then wait for the "New Room" screen to appear.

And then I'm going to paste in that room name that I just copied. Click save. So now we're making a room assignment, a room, and associating it with this x-ray machine before clicking Save. So, returning to our diagram, you can see that we've assigned medical and office equipment to a room. And now, in the next lesson, we'll assign a piece of office equipment to a user.

6. Assigning an Asset to a User via the Hybrid Junction Object

So now I'm going to create another asset. And if you go to the Assets tab, it will display if you're on an asset record. So I've got this X-ray machine asset record displayed.

So far, by clicking on assets, I've gotten a list of two. So if I create another asset, I'm going to call it This will be office equipment. And remember, in this lesson, we want to assign this to a user. And so this will therefore be an employee assignment. And if you recall, we weren't able to do a master-detail relationship. Let me show you the diagram and remind you of this.

As we were trying to create the master detail relationship for employee assignment, looking up the user wasn't an option, so we had to do a lookup. So, my lovely and artistic diagram, this is a little MD here for Master Detail. That is incorrect. To the user, this is a look-up. So therefore, this is what I call a "hybrid junction object," or that makes the employee assignment a hybrid because we have a lookup to the user and a master detail up to the asset.

And I don't know if hybrid junction objects are a thing or not. I'm trying to make it a thing by calling it that. I even Googled "Hybrid JunctionObject Salesforce" and wasn't finding much. So maybe we'll start a trend. All right, so office equipment is a new asset. Yes, please. So let's call this: All right, so before I go further, let me click Save and let's see what's required here because we have these three lookup fields, and some of these may be required. An asset needs an account, a contact, or both.

And I think it needs both, actually. And so in this scenario, if you're assigning office equipment to an employee, and we'll be doing this later, we'll be doing the employee assignment through that hybrid junction object I just spoke about. However, because it is associated with your own company and not, say, a client company, you would enter your own company name here. So let's just say internally, we're working for Dickinson Plc. For example, let me click Save and see if we have to have a contact as well. and we didn't. All right, so we've created a laptop record and associated it with the Dickinson Plc account. And so now we need to assign this to an employee. This will be one of our own employees.

And in this scenario, we are working for Dickinson Plc. So now if we look in the related list, you probably won't see employee assignment, and there's room assignment. So if we wanted to assign this laptop to a room, we could do that like we did in the previous lesson. But what I want to do is edit the page layout and also include an employee assignment-related list. All right, so we're going to click EditObject to go into the Object Manager. Once again, select the asset object and then select Page Layouts. And remember, we just have the one-page layout. Currently, for the asset layout, we'll edit that.

That opens up the page layout editor. We'll go into more detail in the related list. And now for employee assignments, we'll drag that down as well. And then we'll just trust that we have the buttons we need rather than pausing to resize my display, clicking Save, and then yes. And we'll look at this laptop record over here in this other tab now, refresh, and see that related list in action. So, if we go back through this related list on this laptop record, we see that we don't have any employee assignments or room assignments for this office equipment.

Now, if you recall our diagram, let me zoom out. Our office equipment is listed as an asset. Remember, this is just the one object. There are just two different types of records. For medical equipment, we want to be able to assign it to a room. And for office equipment, we also want to be able to assign office equipment to a user as well. One note to make is that we don't want to assign medical equipment to a user. And so what we're going to do after we assign this laptop to an employee is introduce a new page layout so that the medical equipment page layout only has room assignments but not employee assignments. makes sense, hopefully. Let's go.

All right, so we're going to assign this laptop to a user who would be an employee. I'm not seeing the lookup on the employee assignment page layout for the user. So let me click save. I need to add that to the page layout as well. What I've done is create the employee assignment, but I've not associated it with the user. So I'm going to now click on that employee assignment record. So now I'm in an employee assignment record, and I'm going to click on Edit object from the gear icon here to get into the employee assignment object inside of Object Manager. And then I'll go to the page layout there.

So you begin to get a feel for real-world scenarios here as you're building an application and making it a reality; it's kind of like ironing a shirt. You just do it one layer at a time, go over it multiple times, and eventually you get it right. So far, we've got the one-page layout. I'll update this, and here is our user lookup, labelled "employee." We're going to bring this down into the details section. And what you can do here is divide this into two columns. Let me move this over here so that it takes up the majority of the screen. real estate, click save. So now, if we go back into our employee assignment, let's refresh this.

And so now we see the employee lookup field, so we could come in here and search for people. This is a look at the user records. And these are the active users in my d come iSo I'm going to assign this laptop to Jim Doe in this example.

And so now, if we revisit our diagram, remember, we want to be able to assign office equipment to a user and medical equipment only to a room. And so that means we need to create an additional page layout. If we go back into our equipment Allow me to enter and bring up assets. I was trying to get to the Assets tab. We don't really have it set up yet.

So we have medical equipment here, this X-ray machine. And we need to take away the capability of assigning a medical device or medical piece of equipment to an employee. So we have the employee assignments. As a result, we must now develop this use case.

We need to create additional page layouts. We've already introduced the different record types on assets. And that's just a matter of introducing the corresponding page layouts. So if we go into Edit Object and then Page Layouts, we have the one asset layout. So we'll either clone it or save it as. Actually, I was thinking there was a clone button. I forgot about that.

So we go into Edit, click the down arrow to Save As, and then we can name this medical equipment layout. And so now, for the medical equipment layout, we don't want to assign medical equipment to employees. I'm going to delete this related list and only keep the room assignments, then click Save. And so now we've got a medical equipment layout.

And then we need to rename this office equipment layout. If I go back into Assets, you'll see that I have three page layouts. I really only need two. We'll just leave it at that for now. But what we can do is coordinate these page layout assignments across record types. And so now we can edit the assignments so that we can assign the medical equipment page layout to the medical equipment record type. And then we could as well click the asset layout in this far column here for office equipment and select office equipment layout to change that. Click Save.

So, instead of seeing employee assignment-related lists, we should see on a medical device or equipment that we should refresh. So let's see if this disappears, and it does. So we can only assign medical equipment to a room. And then, as well, let me find a piece of office equipment and go back into setup or the app launcher. I should say, "Go to assets." And for our office equipment, we should see employee and room assignments. So there you have it. We've explored the depth of what is implied through this lovely piece of artwork.

And we have looked at not only junction objects but also hybrid junction objects with a look up.Instead of two master detail relationships, it has a lookup and a master detail relationship. And we've dealt with the implications of leveraging a junction object across multiple record types, which has introduced different page layouts.

And then, as well, we were able to assign assets to a user through that lookup record as well. And so now in the next lesson, I want to talk about some different field type considerations and some other things you may encounter on the exam that are related to the different relationship types as well that you need to understand in order to succeed, not only on the test but also on the job. So I'll see in the next lesson.

7. Considerations for Relationships

On the advanced administrator exam, you'll need to be pretty close to mastery on the different considerations for relationships inside of Salesforce. This has to do with field type conversions and record deletion considerations. So I'm going to link to this Help article known as Consideration Relations for Relationships as a resource in this lesson. But I wanted to walk through and demonstrate some of this as well as just mention some of the high points.

You don't have to remember everything in this Help article, but I wanted to take the time to highlight the things that I know will be of particular interest on the exam, and working as an advanced administrator on the platform, and I've mentioned this before, is that each custom object can have up to two master detail relationships.

So that's the limit on the number of master detail relationships that you can have on a custom object. You can now have many lookup relationships, so keep that in mind as you try to solve a problem on the platform: the maximum number of lookup relationships on a custom object is a master list of detail relationships.

Another thing to keep in mind when it comes to master detailed relationships is that a standard object cannot be a child and a custom object cannot be a parent. Another important note is the conversion of relationships. And I've run into this before, and I'll try and demonstrate how this works here momentarily, but you can convert a master detail relationship to a lookup relationship as long as no roll-up summary fields exist on the master object. And you can convert a lookup relationship to a master detail relationship, but only if the lookup field and all records contain a value. Let's say, for example, that our room assignment is the Room object.

I think a good thing to think about with our solution for asset management is that the presumption is that we're just dealing with one building that contains multiple rooms. But what if we needed to introduce another custom object, and that would be one that could contain these rooms? So on the Room object, the room would be the child of the parent of Building. So let's create a custom object called "Building," and then we will make a relationship between Room and Building and determine if we need Master Detail or look it up. We'll also try converting it back and forth between Master Detail and look up.

So I'm going to go into Setup, and we're going to create this building custom object the more traditional way, just through the Setup menu rather than through the schema builder this time. and go into the object manager. And you see here, if you look at the custom column here, you'll see which are our custom objects that we've previously created, and we want to create a new custom object and call this building. And I just entered in a description that this is the parent object for the Room Custom Object. And we will just leave the default for the name label reading "Building name." And then the data type is tax. We don't want to auto-number these. And then I'm going to select everything at this point.

Allow for searching if you put it in development. And these are the two items that I never could remember that are only available upon creation. Adding notes and attachments to the related list and launching the new Custom Tab Wizard So that's not available through the schema builder. So therefore, we didn't create a tab previously with our other custom objects that we created through the schema builder. So I'm going to click save.

And now I've created my custom building object. The next step in the wizard is to choose the Tab style for Buildings. I think I'll select "Building." It's kind of nice to find something that matches. Then we'll create this Custom tab. So far, we have yet to allow me to turn this on for all profiles. And then the next step of the wizard is where we would include this tab with an application. Now in the next lesson, we'll create the actual asset management application. So for now, we just leave all these unchecked and uncheck this as well, and click Save. So now we have the ability to create custom objects.

So if we go to filter relationships, we need to decide if we want to do a lookup or a master detail. And we need to do that in the room, not the building. So let me go back into Object Manager. And so now that we have our building custom object, we need to create a relationship between the building and the room. Remember that whenever you establish a relationship between a parent and a child, you will do so on the child object. And that would be "room" in this instance. So if we go into the room object and select fields and relationships, it is here that we will determine and make a decision. And we'll alternate between Master Detail and look up. And it's very important to realise that these points of distinction for the master-detail relationship mean that they are required on all detailed records then.

That means you can't have a room unless it's inside of a building. So you need a corresponding parent record for the building that this room resides in. And then as well, the ownership and sharing of the room record are determined by the master record, which would be the building. So that implies some implications for clinical.org. Wide defaults are set for the building, and that will determine the level of access for the room, its ownership, and the sharing of it. Another distinction between Master Detail and Lookup is that when Auser deletes the Master Record, which is the building, all detail records are also deleted. So if we were to get rid of the building, we're also going to be getting rid of all the room records as well.

Whereas with a lookup relationship, you have options on what happens whenever the building is deleted, what happens with the rooms, and you can also create roll-up summary fields on the master record to summarise the detail records. So, for example, we're on the room object. If we want to be able to tell at a glance at the building level how many rooms are in this building, we could make this a master detailed relationship, and then we could do a roll-up summary field on the building to count up the number of rooms.

So we'll start with that as our scenario, and then we'll see what the implications are if we change this to a look up instead, and so on. So we're going to click next, and we're relating this to building. Another thing to note is that you cannot relate an object to itself in a master detail relationship, but you can for a lookup. There's a tidbit there; at least, I believe I'm correct.

You can put that to the test. And I always tend to err on the side of allowing reparations rather than not doing so. If I enter a room and associate it with the wrong building, I could repair that room to a different building rather than having to delete it and create a new room record.

And we could create lookup filters here, but let me just show the filter settings, and I like to click on the "insert suggested criteria" button just to see if there's anything that makes logical sense. And I'm not going to do any of these because it doesn't really matter that the user ID or the room owner ID match. So I'm not going to introduce any filters.

I'm going to hide that and then click Next, and I will make this field visible, and it is visible for all profiles because it's a master detail; therefore, it's required, so you can't make it invisible. And then we're going to add it to our room layout, page layout, and click Next, along with the related list label. So on the building records, the related list will read as rooms, and the page layouts that will include that related list will be the building layout. Now, if I uncheck this, then the related list will not be selected.

So here's another thing with creating custom objects this way and using the wizard: you have the opportunity to get more specific with your related list designations. We had to go in and manually do that for other related lists whenever we created those other custom objects. So I prefer creating objects this way. Actually. I'm not going to bother with a Pin-related list of existing user personalizations because we don't really have any users in our.org.

And this is perfect. This is a great example of the note here about how, if there are records already existing, you cannot create a new master-detail relationship on an existing custom object. and let's see if that is noted here. Yes, here it is, right here.

You can't create a master-detail relationship if the custom object already contains data. You can, however, create the relationship as a lookup and then convert it to a master detail if the lookup field in all records contains a value. And I've run into this more than once in the real world and even in my courses as well. And so it's unfortunate that Salesforce waited until now to warn you about this. At the first step of the journey, once you select Master Detail, it should give you this warning rather than letting you go through all six pages of the wizard. So we're going to click here to return to the previous page. And now we've lost all that progress, basically.

And so we're not able to do a master detail at this point for the building. But let's say that we really want it to be a master-detail relationship. The problem is, we already have a room in our system. Now, you've got a couple of options. You could delete any records that you have in your.org, but that's not advised because then you'll have data loss. Or you can try again and introduce your relationships between rooms and buildings as a look up. And then you can decide what would serve you best—if you want to keep it a lookup or if you want to convert it to a master detail.

So our only option at this point is to make it a lookup relationship. Then, in order to convert this field type to master detail relationship, we'll need to populate any existing records with data in this new lookup relationship field lookingup to building, so that all room records have a building designation. So we're selecting "look up" and clicking "next," relating once again to building. Remember, we're on the object in the room, and we're establishing the relationship from the child to the parent, from the detail to the master.

But this is a lookup, so hopefully it doesn't confuse you. It's a lookup field, so I'm going to leave it at "This is the child that we're on, and we are establishing the relationship by looking up to the parent of Building." It is the building that contains the rooms; click Next to tab out of there. And here is where we have some options on what happens. The lookup record is deleted. And so what happens, for example, is that the lookup record would be the building. So what happens to the rooms if the building is deleted? And that was one of the points of consideration under "Lookup," which is here in this Help article, where there are notes around what happens whenever you're dealing with deletions.

And these options either clear the value of this field or don't allow the deletion. If we go back here, you'll see that we don't allow deletion of the lookup record. That's part of a lookup relationship. So this would block the user from being able to delete the building, or the other option would be to clear the value of this field. And so if we clear the value of the field, then on the Room record we would have this field called "Building" as a look up.

And if that building is deleted and we chose this option, then this field would just be cleared of its value. It would be deleted. Now we can't do that if we make the field required, however. So I'm going to block the user from allowing this to be deleted. So I'm going to click next. And now that it's not required at this point, we can change the visibility and hide this from certain profiles. We can make it read-only.

For example, I'm just going to accept the defaults and click Next and Next again to add this lookup field to my page layout, keep the related list label the same, and click Save; it should now succeed now.So we've narrowed our search to "building." If I go into edit this to try to change the field type, if you will, and select Master Detail Relationship and just next on through here, it will most likely give me an error because I haven't even created a building. and that's correct.

So what I have to do is create a building, and then any rooms in my.org need to have a building specified. And so if I go in, let me look at how many rooms I have. I think I just don't remember. Actually, I have one, two, or 10 billion. Okay, so I've got the two rooms. If you notice, we've got the details, and there's no building associated with this record. So all records in my.org for the room need to have a building associated with them. And then I can convert the field type over to Master Detail once all records contain a building designation.

Now, I don't have a building yet, so we're going to create a building. We'll call this corporate headquarters and save it. And now, if we go back into the Roomstab here, let's go into the other room and specify a building for it as well. I'll just make it the same building as corporate headquarters and save it. And so now, if we go back in, we should be able to flip the field type of building on the Room object from lookup to master detail.

Let's check it out and hope for the best. Shall we? Edit an object in the room? We're on the record. So Edit Object then filled in some relationships, and we once again want to try to change this data type. We want to change it to master detail because it's looking up. We've populated all the records in our.org with a value from that look up. So we're going to change the fill type of the master detail now.

We're just going to move on through here. And so now it's updating the records, and we have successfully changed the data type from lookup to master detail. So, for the most part, become very familiar with all of the ins and outs and caveats.

And I previously highlighted the things that are really important, and I don't think you need to worry about things like multilevel many-to-many relationships. I don't recall seeing that on the exam. That gets pretty hairy. But that's hard to know. Relationships with external objects, I don't think you need to be concerned about either.

But when it comes to what happens when you delete or change a relationship, when you convert relationships, and when it comes to self-relationships, you should be aware that it is a possibility. So now that we've done all of this, let's actually create the application for the asset management app, and we'll do that in the next lesson.

8. Creating the Asset Management App

There are several ways you can create an app now inside of Salesforce, thanks to the Lightning AppBuilder, for example, and the App Manager. And so if I click on the app launcher, here are the different apps that I currently have available to me here in Lightning Experience. As a result, the ultimate goal is to add an Asset Manager app to the app launcher.

And so, for example, I could go into the App Manager inside of setup, which brings you to the Lightning Experience AppManager, and you can create a new Lightning app. And so let's create this asset management app this way. And I'll show you another way to create an app momentarily. Give the app's name and the developer's name. You can do custom branding as far as the logo and colors; I'm not going to change any of that. This is what this will look like. I made a note here.

This is built using the app Manager. Clicking next. And then here, you can provide either standard or console navigation. And so I'm just going to leave this as standard navigation and not make this a console application. And then I'm going to provide the regular setup menu and not the service set up.and I'm just going to leave the defaults here. I'll allow end users to personalise their navigation items in the app. And then a utility bar appears across the bottom of the application. And if I add a utility item, then I can select from several different options here below. I'll go ahead and add the History utility item and click Next. And for the navigation, we want to select the tabs that we want to include in our app. And so we would want assets. And then, as well, it would make sense that buildings come into play. And then, as well, we could have rooms.

Then there are some other common objects you might want, such as contacting an account. So as you're making these distinctions, you want to think through what the related objects are—basically the things that we had in our diagram that we may want to include because we may be called upon to create new products, for example. And it'd be nice to have that as one of the navigation items. It'll go through and see if there's anything else I need to do before I just click Next. And then for the profiles, you can select one or multiple profiles to make this app available to I'm just going to select all profiles, save, and finish. And so now we have our asset management application. Now I want to show you something that we did through the Lightning Experience App Manager.

And it shows that it is a Lightning app, not a classic one like some of these others. And you could go in and edit by just clicking here. But I wanted to show you what it looks like as a mobile preview via the Salesforce Mobile Quick Start. And this is just one method of previewing what you write. org appears in mobile mode, and it may crash out, crash, and burn for me. And I'm probably going to have to change my display because it's just blown up too big. So for navigation menu items, I wanted to show you what we have here. So out of the box, there's no selection for the asset management application. So, let me return to setup and show you in the mobile navigation or Salesforce navigation. It's not available on mobile.

So, one thing you can do, and this is the other way that it's kind of preferable nowadays to build an app rather than the Lighting Experience, is to use the Lighting App Builder. And through here, you can create a Lightning page to then make that available in both the Lighting Experience and on mobile. And I wanted to mention this because not only is this not necessarily going to be on the exam, but this is kind of a departure from what you may be used to as a classic administrator if you're migrating over to Lighting Experience. And so you can create a lighting page for an app, and we're going to do that for our asset management application. So we'll click Next, and we'll give it the label of asset management. And one thing I thought of was, I'm going to pop over to a different tab at this point so I don't lose my place, but let's look at the App Launcher to see if our asset management app shows up in the App Launcher.

I think it should. And there it is. So here's our app instead of Lighting Experience, so it is available in Lightning Experience. The main thing with the Lighting App Builder that we're starting to go down the path of in this other tab is to make it available on mobile. But here's our asset management app with the different tabs that we selected to make available in our application, all in one handy location. Pretty cool. Back to the lighting app builder.

We're going to select a layout for our page, and I'm just going to select "Aheader" in the left sidebar and click Finish. And then we can start to drag these Lightning components into the Lightning App Builder. So what I do is usually different for everyone, and it really doesn't matter; you just want to be consistent with whatever the company you're working for prefers or has as a standard. And here is where I usually put a header in place. And this is a WYSIWYG editor.

That was a rich text component that I drove onto the canvas there. And you can adjust the font size, for example. And so here is my Lightning component for that rich text. And then as well, you can include other components. So a good example of it being like a typical Lightning app is that you might have a dashboard. We don't have any dashboards right now.

I don't think we have any dashboards, actually. Yeah, we don't. It would most likely be beneficial to create an asset management dashboard. For the sake of time, I'm not going to do that. However, dashboards are frequently found on the application's home page, particularly in lighting apps. But you can include a chatter feed, for example, and the different feed types are bookmarked or things that I follow or things that have been chatted to me, for example. I'm just going to make this what I follow, though. So we have a chatter feed. We could add a list view. I'm going to drag this up above. Let's move it here, list view.

And here is where you can get into actual assets, for example, and you could show more than three. You can do 30, for example, and that might be a bit excessive. Let's do twelve. And let's not get too complicated at this point. To save this Lightning page, simply click Save. So now we have saved the page, but we need to activate it to make it available to users. And so we click "activate." And so it's here that we have three different tabs. There are page settings, lightning, experience, and mobile. So under Page Settings, we can activate this for all users or system administrators only. We can have an icon that we can change here.

So if we want to change the icon for Asset Management, here are some nice Lightning icons. I'm not sure what to select for assets, so we're just going to select that randomly. And then let's click on "Lighting Experience." And here is where we can add this page to an app. Here are the different lighting apps: So we're going to add this page to this app by clicking here after selecting Asset Management. And so now we've got our different tabs related to asset management, and we can move them up and down. That's for the Lighting Experience, and then for mobile, we want to add this page to the mobile navigation menu.

So here's our Asset Management application, and that is now a new item in our navigation menu for mobile. You can also move this up, for example, and then click Save. As a result, activation was successful. So let's go back to a different tab. I don't want to lose my place. There's going to be set up, and now if we go into the mobile navigation, we should see Asset Management. There is Asset Management, and it's at the top because that's where I selected it to be. So if we look at the mobile quick start, let's see if we can see this a little bit more in action. Sometimes I like to do this just to visualise what it will look like, but it's not showing up, of course. So I think that's a caching issue. Let me refresh and see if I can force it along. Lighting does cause caching issues sometimes. Let me start again. And here's asset management. Awesome.

So, all right. We've done a lot here in terms of custom object and application extension. And I felt like it was important to actually create an application in order to understand the concepts of this knowledge area. And we've covered a lot of ground. And this is the second knowledge area of the advanced administrator. So we've looked at junction objects, hybrid junction objects, master detail relationships, look-up relationships, and we've even built an app and made it available in mobile and lighting experiences as well. And so, as we finish out this knowledge area, let's prepare for the next knowledge area.

Prepaway's Certified Advanced Administrator video training course for passing certification exams is the only solution which you need.