Views determine the way records are displayed within a table, such as the fields that are displayed, row ordering and colors, layout, and the number of records per page. Views allow individuals and teams to have their own settings for the same table.
Planning and Managing Views
Every table should have at least two views: a default view with the key facts for that table's records, and another view with more detail and more fields. Tables also always have three Default Views: Personal, Mobile, and Summary.
If you embed the table in the records of other tables, you should also design a view specifically for that use to remove repetitive information. For example, in the default view for the People table, it makes sense to show the Company field, but if you embed the People table in a Company record, the Company field would show the same value for each record. Instead, create an additional view in the People table that does not include the Company field.
Admins can create views and apply them to teams of users, making them available in the drop-down or the default view for that table. See Views and Permissions for more information.
Saved searches can be configured to apply a specified view when the search runs. This is particularly useful with hierarchical data, as different subtables often have different optimal views of relevant fields. For more information, see Using Saved Searches to Work Efficiently.
Creating and Editing Views
To create or edit a view:
- From a table's action bar, click Views.
- Choose whether you want to create a new view or configure existing views:
- Select New to create a new view.
- Select Edit to edit the current view.
- Select Manage to display all the existing views you can edit for the table. Then, click the edit icon for the view you want to edit.
Use the the Fields tab to configure field and record display options.
- Select whether the selection checkboxes and different icons are displayed. Generally, you should at least include an edit icon.
- Select the maximum lines to display per record and per linked field. For a clean look, this should be set to 3 or fewer lines.
- For each field you want to include in the view:
- Select the Display checkbox so it shows in the view. Only display relevant fields; showing too many can make the list slow to load, while showing too few can slow down user productivity.
- Set the Column Width and Column Width Size, if desired. Users can adjust the Column Width by clicking and dragging the column borders in the table view. In most cases, you should select Automatic, but for Date/Time fields, set the width to 14 to force the data to wrap onto two lines.
- Add a Cell Link, if desired. To save space, you can show the ID field and set the Cell Link field to View instead of showing a view icon. This is also useful for views used in reports, so users can jump from the report directly to the record.
- Select the Quick Edit checkbox if you want users to be able to edit the field directly from the table view. This is only available if the field is configured to allow it, and if your group permissions allow you to create Quick Edit views.
- Select the Quick Search checkbox if you want the field to appear as a default option when users click Search from the table view. Adding a field to Quick Search makes it easier for users to filter records based on that field.
- Select Right Align for fields whose content should be formatted this way. This is typically only used for currency.
Use the Order/Colors tab to select the order in which fields are displayed, as well as the row coloring and notification icons. Users can adjust the column order by dragging and dropping if they need to, but it won't overwrite the default order defined here.
- Drag and drop fields into the left-right order you want. If you are editing an existing view, newly added fields appear to the far right. In general, always place the ID field in the leftmost position, and continue from there placing the most relevant fields to the left of less relevant fields.
- If you have a lengthy text field that you want to show across the full width of the screen, drag the field name down to the No items to drag area. The content of a field in this position is shown without a field label. In most cases, try to keep record information on a single row to improve readability.
- Click Set Row Coloring and Define Notification Icons to define row coloring, fonts, text highlighting, and icons. See Row Coloring and Notification Icons for more information.
Use the General tab to configure settings for the view.
- Enter a name for the view.
- Set whether the record can be deleted.
- Define a maximum and minimum view width, as well as a minimum field width. For these, we recommend:
- Set a Maximum View Width of at least 100 to 120. The best choice depends on the fields in your view and the number of characters in those fields.
- Set the Minimum View Width to Same as Action Bar. When this is set to None, the view is only as wide as the data being displayed, which can sometimes look too narrow.
- Choose how many records to display per page. If pages take too long to load, consider lowering this value. A reasonable starting number is 30 records per page.
- Select whether cell borders are displayed.
Use the Apply tab to choose to which teams have access to the view. This tab is only visible if you have permission to publish views to other users.
- Choose whether to keep or change the current visibility settings for the view. If you choose to change them, you must also choose whether the view is available to yourself, which teams can see the view, and whether subteams and new teams can see the view.
- Choose whether to keep or change the settings for which teams have the view as a default. If you choose to change them, choose whether the view is the default for yourself, which teams have the view as a default, and whether subteams and new teams have the view as a default.
- Click Finish.
Team membership affects default and available views:
- A user on multiple teams can see all views that are available to any of their teams.
- A user’s default view is the default assigned to their primary team. A team has only one default view.
- The user's personal view is their primary team's default view until the user customizes their personal view.
Known Issue: Disappearing or reappearing table borders
Showing borders around rows and cells in a view is one of the settings in the View wizard. However, a setting in the Look and Feel wizard can override the settings in a view. If you see borders but the view doesn't have borders applied, or if you don't see borders but the view does have borders applied, check the following setting:
- Go to Setup > Look and Feel.
- Click Power User Interface or End User Schemes to resolve the issue in the corresponding interface.
- Edit the look and feel scheme that is applied to the users experiencing the issue.
- On the Tables tab, check the settings under Table Border and Cells. The Table View Borders Visibility setting can override settings for all views.