Managing List Views

List views group module records using selected fields and filter criteria so users can focus on relevant data. They help subscribers work faster by showing only the records needed for a specific task, such as follow-up records, region-specific records, or stage-based pipelines.

For example, in a property management application, you can create an Open Properties list view to show active listings and a Booked Properties list view to display units with reservations or confirmed bookings. This helps teams switch between general operations and booking-specific workflows without changing the underlying module data.

You can use system-defined standard list views provided for each module, and you can also create custom list views for business-specific needs. Custom list views are packagable components in Vertical Studio. When you publish your application, packaged custom list views are included in that version and available to subscribers during signup or application upgrade, based on packaging behavior.

Where to access and configure list views

Log into your Developer Console.
Navigate to Build > Components.
Open Custom View Settings.
Select the target module from the module list.
Click Create View to add a new custom list view, or open an existing list view to edit it
In the New View page, do the following:

Enter the custom view name.
Select the columns to be displayed in the View mode.
Specify Criteria to filter the records.

Click Save.

The Custom View settings are available in both the Developer Console and the Subscriber Organization. However, the Share With property is available only to the Subscriber Organization.

List views are fully packagable. Any custom list view created here is included when you publish your application and available to subscribers when they upgrade, subject to the upgrade type of each property.

Sample use case

In a property management application, a sales team needs a quick view of properties that are ready for walkthroughs, while the operations team needs a separate view of properties already assigned to clients. You create a custom list view named Open Properties with columns for city, bedrooms, monthly rent, and parking availability. You also create a Booked Properties view with columns for assigned client, furnishing status, and available-from date.

After publishing, subscribers can use both packaged list views immediately. They can rename either list view, change the visible columns, or apply local filters.

Standard and custom list views

Vertical Studio modules include standard list views and custom list views.

System-defined standard list views are built-in views available for immediate use.
Custom list views are user-defined views created with criteria and selected columns.
Packaged list views are custom list views created in the Developer Console and delivered with your application version.

In subscriber orgs, packaged custom list views are available under Created by Me. System-defined standard list views are available under Public Views. Once a packaged custom list view is available in a subscriber org, that list view instance is subscriber-owned and follows the packaging and upgrade behavior defined in this document.

Manage columns in list view

You can tailor list readability by choosing which columns are shown and in what order.

Open the target module list view.
Add criteria for the list view. Only records satisfying the criteria will be displayed in the view.
Select the column management option in the list header.
Add or remove columns based on the requirement.
Reorder columns to keep high-priority fields first.
Save the view.

If your interface includes column controls, you can also use sort, hide, and pin options for faster navigation in wide lists.

Packaged Custom List Views

A Packaged List View is a custom list view created in the Developer Console and included when you publish your application. Subscribers receive packaged custom list views during signup or when they upgrade to a version that contains eligible packaged changes.

In subscriber orgs, packaged custom list views appear under Created by Me, while system-defined standard views appear under Public Views. For upgrade behavior, treat packaged list views as packaged custom list views, not as system-defined standard views.

To learn more about packaging behavior, refer to Components and Packaging in Zoho Vertical Studio.

Property	Upgrade Type	Subscriber Modify Access
Custom view name	Non-Upgradable	Yes
Criteria	Non-Upgradable	Yes
Selected columns (fields shown in list)	Non-Upgradable	Yes
Lock status	Non-Upgradable	Yes

Action	Upgrade outcome for existing subscriber orgs
Create a new packaged custom view in Developer Console	Upgradable. The new view is added during upgrade.
Delete an existing packaged custom view in Developer Console	Non-Upgradable. Existing subscriber orgs retain the view during upgrade.

Publish and version upgrade

General behavior

Adding a new custom list view is upgradable and is delivered to existing subscriber orgs during upgrade.
Editing an existing custom list view in the Developer Console is non-upgradable for existing subscriber orgs.
Deleting an existing custom list view in the Developer Console does not remove that list view from existing subscriber orgs during upgrade.
Subscriber-side edits to a custom list view are retained in that subscriber org.
If a subscriber deletes a custom list view, later developer edits to that same existing list view do not restore it during upgrade.

Example

In an automotive platform application, you can publish a new custom list view such as Apartments and make it available to existing subscriber orgs during upgrade. If you later edit that same existing custom list view, those updates are available to new signups, but are not applied to existing subscriber orgs.

If a subscriber org updates, locks, or deletes its local copy of a custom list view, those subscriber-side changes are retained. A later update to that same existing custom list view in the Developer Console does not overwrite subscriber edits and does not restore a subscriber-deleted list view during upgrade.

When you need to deliver updated logic to existing subscribers, create a new custom list view instead of modifying an existing one.

Changes and Impacts

Since the changes in Custom Views cannot be deployed to existing subscribers through an upgrade, there will be no impacts to the existing records in the Subscriber's organization.