Edit Field Properties across Multiple Layouts

Consider a custom object named Ticket for which you want your users to always enter an account while creating a ticket, but not when they're importing a ticket from an external source.

To do this, you can set the Account field as required across all the creation page layouts. Here, Ticket is a custom object that can be created. To implement this worked example, use a custom object created in your own environment.

This example illustrates how to perform a mass update of the UI properties of the Account field across the creation page layouts.

Perform a Mass Update of the UI Properties of a Field

1. Navigate to the Creation Page Layouts section of the Ticket object.

2. Click Actions and select Edit UI Properties from the drop-down list.

   The Edit UI Properties page appears.

3. Select the Account field from the drop-down list.

   The Field Definition section displays the current properties of the field at the model level. Note that the Required property is set to No.

   The Layout Properties section displays all the active layouts for the field.

4. In the Layout Properties section, select all the layouts.

5. Click Update.

   The Update Layouts page appears.

6. In the Layout Properties section, set the Required property to Yes.

7. Click Submit.

   The Edit UI Properties page appears.

8. Click Done.

   The Account field is now updated as a required field across the selected layouts.