DocsViews
Views are saved query configurations for collections — defining which fields are visible, how records are filtered, and in what order they appear.
A view is a saved configuration that controls how records in a collection are displayed. Views define filters, sorting, and field visibility — like a saved query that can be applied instantly.
What views define
| Setting | Description |
|---|---|
| Filters | Conditions that narrow which records are shown |
| Sort order | Fields and direction (ascending/descending) for ordering records |
| Field visibility | Which fields are displayed and in what order |
| Field width | Display width for each visible field |
Use cases
Views are useful for:
- Team-specific displays — a sales view showing deal stage and value, a support view showing priority and status
- Workflow stages — "New leads", "Qualified", "Closed" views that filter by status
- Reports — sorted and filtered views that highlight specific data patterns
- Data entry — simplified views that show only the fields relevant for input
Creating views
Views are created within a collection. Each collection can have multiple views, each with different filter, sort, and display configurations.
A view's configuration includes:
- Name — display label for the view
- Filters — array of filter conditions (field, operator, value)
- Sort — array of sort rules (field, direction)
- Visible fields — ordered list of field IDs to display
Default view
Each collection has a default view that shows all fields with no filters applied. Additional views can be created for specific purposes.
Views and blueprints
View definitions can be included in a blueprint's collection schema. When the app is installed, the defined views are created along with the collection. This lets blueprint authors provide useful default views alongside their data models.
Related concepts
- Fields and Types — the fields that views configure
- Records — the data that views filter and sort
Records
Records are the data entries within a collection. Learn how to create, read, update, delete, and query records with filters, sorting, and pagination.
Datasets
How datasets work in the Bivariant platform — structured data storage with partitioning, multiple storage modes, and support for CSV, JSON, and Parquet formats.