Tell Me More: Compact Layouts

We’ve gone over a lot about compact layouts, but here are a few more tidbits about how they work.

If a user doesn’t have access to one of the fields that you assign to a compact layout, the next field on the layout is used.

Removing a field from a page layout doesn’t remove it from the object’s compact layout. The two layout types are independent.

Fields that aren’t available in the SOAP API don’t show up on compact layouts in the Salesforce app.

Compact Layouts and Record Types

If you have record types associated with an object, you can override the object’s primary compact layout and assign different compact layouts to some or all of the record types. Each record type can have only one compact layout assigned to it. If you don’t set any record type overrides, all record types use the object’s primary compact layout by default.

To find out more about compact layouts and record types, see “Assign Compact Layouts to Record Types” in the Salesforce Help.