In thinking about the Salesforce Lightning Experience UI (LEX) from an Admin perspective, there are key differences from the Classic UI that are important to highlight. In this post I’ll review the difference between the ‘Lightning App Builder’ and ‘App Manager’ in the Lightning setup menu and how I remember the distinction between the two. In addition, I will review what is different in terms of configuring Page Layouts. If you are used to configuring in Classic, then you are probably used to Record Types and Page Layouts; however, in Lightning, enter the Lightning Record Page to manage as well. I will dive into how you can think about this new piece to your layout puzzle and the cool new capabilities that Lightning Record Pages offer you.

Lightning App Builder vs. App Manager. These sound basically the same, but one manages your app pages and one manages your apps…huh?!

Lightning App Builder is where you ‘build’ your individual Lightning Record pages:
Screen Shot 2020-04-26 at 8.13.20 PM

App Manager is where you ‘manage’ and create your Salesforce apps as you are used to thinking about them:
Screen Shot 2020-04-26 at 8.15.18 PM

How about Record Types, Page Layouts, and Lightning Record Pages. Page Layouts are the collection of fields your user will see when they look at an individual record in Salesforce. This is assigned at the Profile Level, so you can vary the Page Layout assigned by Profile. In other words, on an individual record one user could see a completely different collection of fields than the next. Even if they have the same Page Layout assigned, if their profile or permission sets do not give them access to an individual field, they may not see all the fields on the Page Layout.

Then you layer on Record Types. Record Types allow you to vary separate business processes under the same object. Using a simple example, you may have different ways of selling Hardware vs. Software on Opportunities, with different Stages of the sales process and different values available in your Picklist fields. A new Record Type is the way to solve for this. It is important to note that it is best practice not to overuse Record Types as this creates additional overhead from an administration perspective. Along with your new Record Type, you will likely have at least one new Page Layout to manage, and could have multiple, depending if different Profiles need to see different layouts.

When you move to Lightning, you now have this third piece to consider, the Lightning Record Page. This does not replace Page Layouts and Record Types. You can instead think of this as a supplement to give you additional flexibility. The Lightning Record Page is a grouping of components, both custom and native, that ultimately are the page that your end users will see. Your Page Layout will only be one piece of what your end users see on the overall Lightning Record Page. My next post will cover how you can utilize these components to the fullest to surface what your users need to see when they need to see it.

When I was first learning Salesforce, I feel like Record Types vs. Page Layouts was glossed over pretty quickly, so I thought maybe breaking it down in the way that I found useful could help others on their learning path.

I think it’s easiest to think of Record Type first in terms of record creation. When you create a new record (i.e. a new Opportunity, a new Case, etc.), and you have access to more than one Record Type, you will get an option page that pops up to have you select the ‘type of record’ you wish you create (pictured).

Screen Shot 2018-07-09 at 4.16.11 PM

Each of these Record Types can have multiple Page Layouts associated to it, but each Profile will only have one Page Layout assigned/viewable per Record Type. For example, if I am on the Customer Support team, and I am assigned to the ‘Customer Support’ profile, then I will always see the same arrangement of fields and related lists (Page Layout) on every ‘Internal Requests” Case Record Type I am viewing.

Your Record Types are the foundation of the ‘type’ of Object (Object being Opportunity, Case, Account, etc.), meaning I have Cases of type = ‘Customer Requests’ vs ‘Internal Requests’ in the example pictured above. One of the big things you can do with different record types is vary your picklist values (on picklist fields) and have different Support Process (Cases), Sales Process (Opportunities), and Lead Process (Leads) statuses. Your Support Process in Cases are the statuses your Case will go through: New, Working, Resolved, Closed, etc. These can vary depending on the Record Type, and a new Record Type is the only way you can have a different Support Process, Sales Process, or Lead Process.

In creating a new Record Type, you will want to make sure that is warranted: do different teams work these, do they need different picklist values visible on fields, or do they follow a unique process (in terms of status changes)? If you just need a particular Profile to see different fields, then you may just need a different Page Layout or even use Field Level Security to limit visibility of fields on the same Page Layout. Think about whether this is truly a different kind of Case, Opportunity, Account, etc. Do you have different types of Cases needed or do you just need a different page layout for the same type of Cases for different people?

Break it down:

  1. Different Profiles have access to different record types (which types of cases can you create and edit?).
  2. Note, that all Profiles with access to an Object can view all Record Types, but cannot necessarily edit or create records of that Record Type.
  3. Different Profiles have access to different page layouts (You may see different fields and related lists on the same Record Type based on your Page Layout assignments at the Profile level. You cannot use Permission Sets to assign a Page Layout.
  4. For each Record Type and Page Layout combination, you have one Page Layout assignment per Profile. In other words, each person can only have access to one Page Layout per Record Type of a particular Object.

I’m super excited to build out this blog and hopefully help others on their journey in the Salesforce ecosystem. I welcome all feedback and questions as well!

Hi, my name is Lindsey Fivecoat, and I love Salesforce! As my dear friend Martin told me, how to succeed in Salesforce Fivecoat style: fall in love with Salesforce, never stop learning, and become a Salesforce swag hag (truth).  I’m not going to tell you an accidental admin story, I will explain to you how I purposefully chose to dive into the platform and find my way to professional happiness at a level I didn’t know was possible.

Once upon a time, I wanted to be a professional singer. Instead, I graduated from The University of Texas with a Liberal Arts degree, a 4.0 GPA, and not a single clue what I wanted to do with my life. I’ll be honest, I floundered for a little while.

I first met my friend Ezra Kenigsberg 6 years ago, and that was the first time I was introduced to Salesforce. Ezra is a brilliant Salesforce architect, and when I met him, I had no idea what Salesforce or an architect was outside of building things in the physical world. We just happened to live in the same apartment building briefly, but he spoke so passionately about the platform that it really stuck with me. I didn’t see Ezra for nearly a year, but then 5 years ago, I was very fortunate to be hired on in an HR & Recruiting role at a tech company called Bazaarvoice. I walked in on my first week, and who did appear, but Ezra. I did not have the confidence at that time to even fathom that I could consider a career in the technical space.

I continued to grow in my career at Bazaarvoice, being promoted to team lead and then manager, but something was missing. I started to notice that I was happiest when I was working on technical projects: helping with large Workday HRIS projects to overhaul our onboarding and automate manual payroll practices. I came back to Salesforce. I used it as an end user, and something finally clicked that maybe I could give this Salesforce Admin thing a go.

In early 2016, I started researching how I could grasp this mystical cloud creature they call Salesforce. I stumbled upon Mike Wheeler’s courses on Udemy and I was off. I was able to go at my own pace in the evening while my then 5-year-old daughter was sleeping. Later that year, a Salesforce position opened up at Bazaarvoice, and I was determined to make the switch. I interviewed against Admins with actual on-the-job experience, but I got the job, and I felt like I had won the lottery. There was not a chance I wasn’t going to make the most of this opportunity.

I really did hit the lottery it turned out because I was given the opportunity to work with the most generous and technically savvy guys on this planet. It was intimidating at first, because each one of them had years of technical experience, and my little imposter syndrome voice was telling me, “are you sure you can do this?”. Finally, I said to her, “who asked you?”, and I just kept working away and striving to do more and know more each day. To this day, every time I understand a concept about Salesforce that seemed insurmountable just a moment before, I feel a sense of pride in myself and adoration in the platform. Even though most of us have moved onto other companies now, my teammates and I still have our own Slack Workspace where we communicate daily and have a free forum to communicate about any Salesforce questions. I truly feel blessed to call each one of them a mentor and a friend (you know who you are!).

I started this blog because I want to give back to my Ohana that has been so generous to me. If you are just starting on the platform, be patient with yourself and just do a little something each day, even if it is just 10 minutes. Consistency is the key here. You are not going to learn all of Salesforce in one day. To quote my dear Ezra, “There is no such thing as a Salesforce expert”. You could see this as intimating, but I find it exhilarating. That means I get to learn something new each day, and it turns out that was what was missing from my life, that continual sense of learning and evolving. So go get yourself a Trailhead Badge: earn one trailhead badge at a time and suddenly you’re a Ranger. #ProudSFDCRanger

A little note about this photo below. This was my first Dreamforce in 2016. My wonderful friends I mentioned above dared me to go pinch Astro’s tush, and yes, I totally did. I realize this is a ridiculous photo, but it makes me incredibly happy, so that’s why I chose to feature it. Live long and Salesforce! ~ Lindsey

“If you’re offered a seat on a rocket ship, don’t ask what seat! Just get on.”  — Sheryl Sandberg