page layout assignment deployment salesforce

• AppAssessor

Articles by role:

• Consultants
• Business Analysts

By Lucy Mazalon

By Ben McCarthy

• Dreamforce Events
• Courses Login

What’s trending

Salesforce Acquires Own Company for $1.9B in Cash: 4 Key Takeaways from This Mega-Deal

Is Salesforce Still a Good Career Option in 2024?

Salesforce Announces Free Marketing and Commerce Expansion Pack to Enterprise Licenses

How to Prepare for the Salesforce AI Specialist Cert: Exams Start September 9!

Salesforce Winter ’25 Release Date + Preview Information

UPCOMING EVENTS

The admin’s guide to flow security: navigating permissions and mitigating risks, implementing omnistudio best practices for performance and scalability, dreamforce parties 2024.

San Francisco, CA

Dreamforce 2024

Dreamforce – house of cloud, guide to page layouts in salesforce.

By Christine Marshall

How you design a page layout in Salesforce can make or break user adoption – good design leads to greater ROI (return on investment), so it’s never too early to start thinking about your users’ experience!

• Which fields are visible (add and remove fields),
• Where blank spaces appear between fields,
• Field properties, including Read-Only and Required,
• Page sections,
• The number of columns in a section and tab-key order,
• Which buttons and actions are included, such as ‘Edit’, ‘Clone’ or ‘Delete’, and in which order, 
• Which related lists appear, and customize their properties (eg. choosing which fields to display).

How to Create a Page Layout in Salesforce

Page Layout Sections

• Detail page (non-edit)

Field Options

Related Lists on Page Layouts

Assign a Salesforce Page Layout

What’s the difference between Page Layouts and Record Types?

What about dynamic forms.

• Available related lists
• Order of related lists
• Columns on related lists
• Mobile layout

Christine Marshall

Christine is the  Courses  Director at Salesforce Ben. She is an 11x certified Salesforce MVP and leads the Bristol Admin User Group.

More like this:

Data lakes vs. data lakehouses: a salesforce admin’s guide.

By Joseph Gaska

Salesforce AI Specialist Certification Guide & Tips

Sf ben salesforce salary survey results 2024-25, leave a reply cancel reply.

Save my name and email in this browser for the next time I comment.

About 30 mins

Learning Objectives

• Challenge +500 points

Discover More

Configure page layouts and record types.

After completing this unit, you’ll be able to:

• Set up the page layout for a record type.
• Create a record type.
• Use a record type to assign a page layout to a profile.

Create a Page Layout for Readers

Article readers and article authors perform different actions and see different fields on a knowledge article, so Maria must create different page layouts for these users. She creates the page layout for readers first. Let’s follow along and see what she does.

• Click Object Manager and select Knowledge .
• Click Page Layouts .
• Click New .
• If you’re basing the page layout on an existing layout, choose it. Maria selects None .
• Enter the name of your page layout. Maria enters Procedure - Reader .
• Click Save .

The layout editor opens. Let’s take a moment to get acquainted with it.

• Knowledge object (1)
• Page Layouts (2)
• Palette (3) —The palette contains Fields, Related Lists, and Mobile & Lightning Actions that you can add to your page layouts. In this example, Fields is selected, so the palette displays available fields. You can also create custom fields.
• Salesforce Mobile and Lightning Experience Actions (4) —This section displays actions users can perform on the page. Drag items from the Mobile & Lightning Actions palette to add them to this section.
• Knowledge Detail (5) —Drag items from the Fields palette to add them to the page layout. In this example, the first section is named Knowledge Details, and it contains Title and URL Name.

Add Actions and Fields

Maria keeps the palette open and consults the list she made with Ada. She’s going to set up the page layout section by section: actions readers can perform, article information, article details, and article properties.

First, she sets up the actions that readers can perform on the article.

• In the palette, click Mobile & Lightning Actions .
• Hover over the Salesforce Mobile and Lightning Experience Actions section.

• Drag Post to the Salesforce Mobile and Lightning Experience Actions section. Post allows users to post to the Article Feed.
• Drag Poll next to Post.

Next, she sets up the Knowledge Detail section. The Title and URL name fields are already there and set as required. She adds one field.

• In the palette, click Fields .
• Drag Summary to the Knowledge Detail section.

Now she creates a section with more information about procedures.

• Name the section. Maria enters Article Details .
• Leave the defaults checked, then click OK .

Maria has to create custom fields to finish the Article Details section. She decides to create the other sections first and then come back to the custom fields. Here’s what she does.

• To reopen the editor after saving, click Page Layouts .
• To reopen the page layout, click Procedure - Reader .
• Create a section under Article Details. Maria uses the following values:
• Section Name: Properties
• Layout: 2-Column
• Tab-key Order: Top-down
• Add the following fields to the first column:
• Article Created Date
• Last Modified by
• Last Published Date
• Add the following checkboxes to the second column:
• Visible in Internal App
• Visible to Customer
• Visible to Partner
• Visible in Public Knowledge Base

Create Custom Fields

Maria has set up everything she can using the fields in the palette. On to creating custom fields for the Article Details section.

The first field she creates is Procedure Audience, a text field for describing an article’s audience.

• Click Fields & Relationships .
• Choose the field type. Maria chooses Text Area (Rich) .
• Click Next .
• Fill out the values. Maria uses these values.
• Field Label: Procedure Audience
• For Length, # Visible Lines, and Field Name she leaves the default values.
• Description: Use this field to identify who follows or executes this procedure.
• Help text: Who follows this procedure?
• Establish field-level security. Maria selects Visible for all profiles.
• Add the field to the palette for the page layout you’re creating. Maria chooses Procedure - Reader . Salesforce adds the new field as the last field in the first section by default. That’s where Maria wants it to go, but she can move it anytime if she changes her mind.

Maria repeats these steps to create custom fields for Procedure Warnings, Procedure Purpose, and Procedure Steps. She makes sure that the fields are in the correct order in the Article Details section.

Here’s her finished page layout for procedure readers.

Create a Page Layout for Authors

The Procedure - Author and Procedure - Reader page layouts are similar. But the author page has some different actions and an extra field for internal notes. The Internal Notes field is available only to agents who can author articles. Maria creates the Procedure - Author page layout from the existing Procedure - Reader layout.

• If you’re basing the page layout on an existing layout, choose it. Maria selects Procedure - Reader .
• Name the page layout. Maria enters Procedure - Author .

Maria changes the actions. Instead of Poll and Post actions, Maria includes: Edit, Publish, Delete Article, Change Record Type, Edit as Draft, Delete Draft, Submit for Approval, Assign, Archive, Restore, and Post.

She creates a custom field for Internal Notes using the following values.

• Data type: Text Area (Rich)
• Field Label: Internal Notes
• Field-level security: Custom: Support Profile . Maria created this profile for Ursa Major when she set up the knowledge base.
• Page layout: Procedure - Author . This adds the field to the Procedure - Author page layout at the bottom of the first new section. Maria makes a note to ask Ada later if she should add this field to the FAQ - Author page, too.

Here’s what Maria’s page layout for Procedure - Author looks like with the new fields.

Create and Assign a Record Type for Procedures

Maria has created two different page layouts—one for readers and one for authors. Now she creates a record type to show the correct page layout to the correct users. How does she know which users are which? By their profiles. Customers see the Procedure - Reader page layout. Agents see the Procedure - Author page layout.

Here’s how Maria creates and assigns the Procedure record type.

• Click Record Types .
• Select an existing record type to use as a template. The new record type includes the picklist values of the selected record type. Maria chooses Master .
• Enter a label for your record type. Maria enters Procedure .
• Enter a description. Maria enters For step-by-step instructions .
• Select Active to make this record type available immediately.
• Select the profile that will use this record type. Maria selects Make Available next to the Customer profiles listed.
• Select the page layout that users with these profiles see for this record type. Maria chooses Procedure - Reader .

All users assigned the Customer profiles see the Procedure - Reader page layout. They can view articles, but they can’t edit them.

Next, Maria assigns the Procedure - Author page layout to agents using the regular profile user interface. Agents can edit articles.

• Enter Profiles in the Quick Find box, then select Profiles .
• Select a profile. Maria chooses Custom: Support Profile , a profile she created earlier.
• Scroll down to Custom Record Type Settings and click Edit .
• Move the needed record types from the Available Record Type box to the Selected Record Types box. Maria adds FAQ and Procedure .
• Choose a default record type. Maria chooses FAQ .

Maria’s configured a new type of article, procedures, in Ursa Major’s knowledge base. To do it, she created different page layouts and assigned them to the correct users via record types. It’s time for Ada to start creating the procedures.

In addition to page layouts, you can also add and customize components on record pages. Maria doesn’t need that level of customization, but you might. To learn more, check out the Lightning App Builder module.

• Salesforce Help: Create Custom Fields
• Salesforce Help: Page Layout Considerations for Lightning Knowledge
• Salesforce Help:  Record Type Considerations for Lightning Knowledge
• Salesforce Help: Create and Edit Articles
• Trailhead: Lightning App Builder
• Salesforce Help: Assign Record Types and Page Layouts in the Enhanced Profile User Interface

Deploy Salesforce Layouts with precision

Piotr Zuralski on September 15th 2022

Deploying Page Layouts on Salesforce causes headaches for many teams. In fact, the hurdles associated with deploying changes to a Layout make many teams resort to manual workarounds, editing the files in code editors or source control.

Many teams tell us that they’ve resorted to skipping Layouts altogether from their deployments, because of the effort required to deploy even one single Layout change. Instead, they’ve been making manual changes directly in orgs, leaving out Layouts entirely from their DevOps process.

To help with deploying these notoriously difficult bits of Salesforce metadata, Gearset has built Precision Deployments to give teams ultimate flexibility and control. This major improvement allows all Gearset users to cherry pick the exact changes they want to deploy to the Layout.

Deploying Layouts really doesn’t need to be hard! Read on to find out how Gearset solves the challenge, and watch this quick demo to see it in action.

What are the main hurdles when deploying Layouts to Salesforce?

There are a few main issues that crop up when deploying Layouts to Salesforce—and these issues become more complicated when you have more than one team member working within the same environment.

The fundamental problem is that Layouts are large metadata items with lots of component parts, and most deployment tools only support deploying the Layout to Salesforce as a whole—in an ‘all or nothing’ approach.

Different manual workarounds have become the norm. It’s very common for the user to download the deployment package, manually edit out the fields in a text editor, then re-upload the package ready to deploy. Checking and editing the Layout in source control, and then deploying it to the target environment is another time-consuming workaround.

Quite often, these Layouts contain test fields and work-in-progress changes that are still being fine-tuned, so not everything is ready to be deployed. This means teams either have to wait for all the changes to be ready or deploy anyway and fix up the Layout later in the target org. Either option is less than ideal and even more of an annoyance when wanting to push changes quickly, keep on top of your orgs, and keep your end users happy.

If that wasn’t enough, it’s really easy to start overwriting existing changes in the target org when another team member deployed their Layout changes before you. If someone skips the proper release process and makes a Layout change directly in Production, it’s hard to keep an eye on everything going on with every team member. If this is an issue you’re facing, it would be worth looking at setting up a monitoring job in Gearset to alert you if there’s a change you want to know about.

All these time-consuming workarounds are tricky and introduce a lot of different steps for things to go awry. Manual workarounds are slow, can throw up errors—and in a worst-case scenario—entirely break the XML syntax of your Layout files.

Live event September 16th-18th San Francisco CA

Blend your salesforce changes easily with precision deployments.

Here at Gearset, we’ve lost count of the times teams have asked ‘How can I only deploy specific fields?’ or ‘How can I exclude a field from my deployments?’. So we understand the need to develop an easy way to cherry pick which exact parts of the Layout you want to deploy.

We built the Precision Deployments functionality to make deploying metadata types like Layouts faster, easier, and less error-prone. You’ll see the full breakdown of the Layout in your metadata comparison results, and now you can select only the specific parts you want to deploy.

Not ready to release one particular section of your Layout yet? No worries! Leave it unselected and come back to deploy it later. Want to select all changes? Easy! Just select the entire Layout file in the main table. Merging your changes with a teammate’s unfinished work? Simple! Leave out any in-progress fields or changes belonging to other team members. It really is effortless, with no overwriting or conflicts in sight.

Permissions can also be a real pain, and lack of permissions on a new Layout is something Salesforce teams struggle with a lot. The good news is that Gearset will now parcel up the relevant permissions with your Layout deployment. So you can deploy specific parts of your Layout, confident that they’ll be visible to the right end users.

Quickly jump to the new location of your fields

Moving fields in a Layout is a pretty normal occurrence when trying to make Salesforce as intuitive as possible for your end users. Gearset helps you identify cases where a field or section has been moved on your Layout. Any field that has a different position in the Layout is marked with a chain link icon next to the select checkbox, which you can use to jump back and forth to verify the moved field’s new location.

To avoid the headache of a failed deployment we’ve added in some new problem analyzers which will now be able to tell you if a new custom field is referenced in a Page Layout but not included in the package—meaning you can fix the issue ahead of time.

It’s your choice: XML or Layout view?

When building Gearset, we listen to our users and make it as easy as possible for you to release changes to Salesforce—no matter what your role is in the team. Enter the new Layout view.

The Layout view when deploying Page Layouts in Gearset is an absolute game-changer for admins. The admin and developer role becomes a little more blurred as we move towards more low- and no-code development—essentially making it easy for anyone to build on Salesforce no matter what their experience.

Regardless of your coding knowledge, teams can now work seamlessly and collaboratively when deploying metadata. Simply swap over from the default XML view to Layout view for a more visual representation of the Page Layout.

In this Layout view you’re able to use the same functionality as in the XML view but with a more friendly, no-code interface. Click the checkboxes and links in the same way to be able to deploy exactly what you need and also jump to and from changes.

The easiest way to deploy Salesforce Layouts

Teams will often dodge having to deploy a Page Layout to Salesforce because of the tricky all-or-nothing approach. But using Gearset to split up the Layout and only deploying what you want will help take the headache out of your deployments.

Precision Deployments is now an option for everyone using Gearset for metadata deployments . Don’t have a Gearset account? No worries, you can sign up to a free 30-day trial and feel confident you’re deploying exactly the elements you want, without overwriting changes or leaving out important permissions.

Ready to get started with Gearset?

• Full access for 30 days
• No credit card required
• Nothing to install in your orgs

Arrange a tailored demo with our DevOps experts. Kick off the process with a 15-minute call to discuss your requirements.

Choose an upcoming live demo to attend and see Gearset in action with the option to ask live questions.

Select a Date & Time

Please choose only one session to attend

Register for demo

What topic are you interested in*, what problem are you trying to overcome, what is the size of your team.

Talk to an expert in minutes with a 4.9/5 customer happiness rating.

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Deploy Flexipage Assignments

I can deploy a flexipage using the flexipage metadata type . But I can't seem to find anywhere the flexipage assignments type . How can flexipage assignments be deployed?

Flexipage Assignments are called ProfileOverride. It is documented here

The metadata looks like the one below, it is a part of a Custom App :

And the package.xml would look like the one below:

• Its like we have to retrieve all/most of the applications to get ProfileActionOverrides. –  Ankuli Commented Nov 11, 2022 at 6:52

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged lightning deployment metadata ..

• The Overflow Blog
• The evolution of full stack engineers
• One of the best ways to get value for AI coding tools: generating tests
• Featured on Meta
• Bringing clarity to status tag usage on meta sites
• Join Stack Overflow’s CEO and me for the first Stack IRL Community Event in...

Hot Network Questions

• Why are some Cloudflare challenges CPU intensive?
• What is the least number of colours Peter could use to color the 3x3 square?
• Increasing vs non decreasing
• What would the natural diet of Bigfoot be?
• Please help me identify my Dad's bike collection (80's-2000's)
• Long table to fit in two pages
• Is there mathematical significance to the LaGuardia floor tiles?
• How resiliant is a private key passphase to brute force attacks?
• Why doesn't SiLU suffer from a worse version of a "dying ReLU" problem?
• Could they free up a docking port on ISS by undocking the emergency vehicle and letting it float next to the station for a little while
• The pronoun in short yes/no answers to rhetorical tag-questions with the generic "you"
• jq - ip addr show in tabular format
• Why does ATSAM3X8E have two separate registers for setting and clearing bits?
• When should I put a biasing resistor - op-amps
• Expansion in Latex3 when transforming an input and forwarding it to another function
• Should I write an email to a Latino teacher working in the US in English or Spanish?
• Does a debt exist for a Parking Charge Notice?
• Can you spell memento as mement?
• Does the Supremacy Clause allow states to retain abortion rights enshrined in each states' constitution?
• How algebraic can the dual of a topological category be?
• How much could gravity increase before a military tank is crushed
• Colossians 1:16 New World Translation renders τα πάντα as “all other things” but why is this is not shown in their Kingdom Interlinear?
• What are the steps to write a book?
• Undead hunger & nourishing gate?

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

How to retrieve Page Layout Assignment for a profile using Tooling REST API?

Using Force.com Tooling API(REST),How do I get the page layout-record type assignments for the given profile id?

Requesting with

/services/data/v36.0/tooling/query?q=Select+Name,+Metadata+From+Profile+where+Id='00eXX000000XXXX'+limit+1

responds with blank nodes for recordtypes etc.

Is it even possible to retrieve the full metadata of Profile object with Tooling API?

In short term, the layout assignment information is listed in RecordType instead of Profile.

When you retrieve whole SObject Describe from this endpoint:

The response have a "recordTypeInfos" section like this:

For each recordTypeInfo, it contains a value called url:

If you send a GET request to this endpoint, in the response you will see the Layout Id in:

So the mapping is already done by salesforce. That layout id reflects the layout assigned to the current user.

Your Answer

Reminder: Answers generated by artificial intelligence tools are not allowed on Stack Overflow. Learn more

Sign up or log in

Post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy .

Not the answer you're looking for? Browse other questions tagged api salesforce force.com tooling or ask your own question .

• The Overflow Blog
• The evolution of full stack engineers
• One of the best ways to get value for AI coding tools: generating tests
• Featured on Meta
• Bringing clarity to status tag usage on meta sites
• Join Stack Overflow’s CEO and me for the first Stack IRL Community Event in...
• Feedback requested: How do you use tag hover descriptions for curating and do...
• Staging Ground Reviewer Motivation
• What does a new user need in a homepage experience on Stack Overflow?

Hot Network Questions

• Correct anonymization of submission using Latex
• Inspector tells me that the electrician should have removed green screw from the panel
• Why is so much of likelihood theory focused on solving the score function equation?
• Why are Mexicans protesting the judicial reform with PJF banners?
• Does Poincare recurrence show that Gibbs entropy is not strictly increasing?
• Does a debt exist for a Parking Charge Notice?
• Is there mathematical significance to the LaGuardia floor tiles?
• DFT warn: LUMO = HOMO
• I want to write a script that simultaneously renders whats on my webcam to a window on my screen and records a video
• Long table to fit in two pages
• Starting with 2014 "+" signs and 2015 "−" signs, you delete signs until one remains. What’s left?
• How resiliant is a private key passphase to brute force attacks?
• Was using an older version of a legal card from a nonlegal set ever not legal?
• 4/4 time change to 6/8 time
• The pronoun in short yes/no answers to rhetorical tag-questions with the generic "you"
• Why do "modern" languages not provide argv and exit code in main?
• How to fold or expand the wingtips on Boeing 777?
• Big Transition of Binary Counting in perspective of IEEE754 floating point
• Did Queen (or Freddie Mercury) really not like Star Wars?
• Is it possible for one wing to stall due to icing while the other wing doesn't ice?
• Transit Visa Requirement with a self-transfer in Paris
• Why would the GPL be viral, while EUPL isn't, according to the EUPL authors?
• The quest for a Wiki-less Game
• I want to be a observational astronomer, but have no idea where to start