Salesforce1 Mobile App Admin Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Working with Compact Layouts

Page layouts aren’t the only thing that you can use to customize how Salesforce data appears in a mobile environment. Compact layouts are used in Salesforce1 to display a record’s key fields at a glance. Compact layouts are designed for viewing records on touchscreen mobile devices, where space is limited and quick recognition of records is important.

Creating and customizing compact layouts for objects isn’t required for Salesforce1, because system defaults are provided out of the box. However, we recommend using compact layouts to put important fields into object record headers—and elsewhere—to help your mobile users get the information they need quickly.

In the full Salesforce site, compact layouts determine which fields appear in the Chatter feed item that appears after a user creates a record with a quick action.

To avoid inadvertent sharing of information through the feed, the fields displayed in the Chatter feed items for tasks created using a quick action are determined by the Task page layout.

Note

In Salesforce1, the first four fields that you assign to a compact layout are displayed in:
  • An object’s record highlights area
  • Expanded lookup cards on a record’s related information page
If a mobile user doesn’t have access to one of the first four fields that you’ve assigned to a compact layout, the next field on the layout is used.

For example, here are screenshots of a merchandise record page in Salesforce1 before and after customizing the compact layout for the object.

Compact Layout Before and After

If you put the key fields that your mobile users need on the compact layout for an object, they can get that information quickly just by scanning the highlights area of the record page.

If you don’t create custom compact layouts for an object, all of the object’s record highlight fields, preview cards, and action-related feed items are driven by a read-only, predefined system default compact layout that contains a predefined set of fields. After you create one or more custom compact layouts, you can set one as the primary compact layout for the object. The primary compact layout is then used as the default for that object.