Data Representation: View Types

Applies to: App Generation projects that use a supported SaaS Engine version

A view type controls how the generated application presents the records for one entity. It does not change the stored record type.

The current generated stack supports table, list, card, calendar, and kanban views.

Compare the view types

View type	Use it for	Main requirement
Table	Dense records with many comparable fields	Fields that work as columns
List	Simple records that users scan in sequence	A clear title and supporting fields
Card	Visual records with key details or images	A small set of important fields
Calendar	Records that occur on dates or within time ranges	Suitable start and end date fields
Kanban	Records that move between stages or groups	A choice or relationship field for columns

Use a table when users compare many records and values. Tables work well for customers, invoices, inventory, and audit records.

Select the fields that users need for scanning, sorting, and filtering. Do not show every field as a column.

Use a list for a compact sequence of records. Lists work well when one title and a few supporting values identify each record.

A list can be easier to scan on narrow screens. It is less suitable for comparing many numeric fields.

Use cards when each record needs strong visual separation. Cards work well for people, products, properties, projects, and media items.

Choose a clear title, important status, and a small group of details. Too many fields make cards difficult to scan.

Use a calendar for appointments, events, bookings, deadlines, and scheduled work.

The entity needs suitable date or date-time fields. Define separate start and end fields when records have a duration.

Do not use a calendar when time is only a minor record property.

Use kanban for records that move between states, stages, or assigned groups.

The column field must be a suitable fixed choice or single relationship. Examples include status, sales stage, team, and assignee.

Define stable column values. Do not use unrestricted text for kanban columns.

Name the entity and required view in your requirements. Explain how users must group, sort, or move its records.

Example:

Show opportunities as a kanban board. Use sales stage for columns and expected value on each card.

For a calendar, name the required start and end fields. For kanban, name the required column field.

Use Edit via Chat and state the entity, new view type, visible fields, and required interactions.

Check the result in the application preview. Confirm that filtering, sorting, forms, permissions, and mobile layout still work.

Available view behavior can change with the SaaS Engine version. Verify the result in your project before production use.