Common View Design Patterns

---

In application design, a single worksheet can contain multiple views tailored to different business scenarios. By combining filters, field visibility settings, and sorting rules, views help users focus on the most relevant information for their tasks.

So, what are the most common ways to organize views in real-world applications?

Organize Views by Record Status

Use status-related fields to separate records at different stages into dedicated views.

For example, in a Sales Leads worksheet, you can create views such as New Leads and Qualified Leads based on lead status.

Organize Views by Record Ownership

Use record owners or user-related fields to display different sets of records to different roles.

For example, in a Sales Leads worksheet:

• My Leads – Displays only leads owned by the current user.

• Team Leads – Displays leads owned by the current user and their subordinates.

• All Leads – Displays all leads the user has permission to access.

This approach is widely used in CRM, project management, customer service, and similar scenarios. It helps team members stay focused on their own work while allowing managers to oversee team activities and performance.

Organize Views by Information Scope

Different users often focus on different aspects of the same record. By configuring which fields are displayed or hidden, you can create views tailored to different usage scenarios.

For example, in employee information management:

• Contacts View – Displays basic information such as name, department, job title, and contact details.

• Employee Profile View – Displays the complete employee record.

By combining field permissions with view configurations, organizations can share the right information with the right audience while protecting sensitive data.

Common Design Pitfalls

Avoid creating a large number of views based on field values that change frequently or continue to grow over time, such as version numbers, regions, or product models.

For these dynamic classification requirements, it is recommended to use filters, quick filters, or grouping instead of creating additional views.

Why avoid this approach?

As the number of views grows, maintenance becomes more difficult, navigation becomes more cluttered, and users may struggle to quickly find the views they actually need.