Both the deck and the table view types have similar capabilities, but your unique use case will determine which view type is a better fit for your application. 

The Table view shows information in a very compact way allowing you to quickly scroll to find a row. The Deck view shows information about each row in a "deck-of-cards" format including an image. If the data doesn't have an image, you should consider adding a virtual column with a thumbnail image constructed with the formula TEXT_ICON(INITIALS([Column_Of_Type_Name]))

In addition to the image, the Deck view will display two text columns as well as any action buttons for phone numbers or emails. The display columns are chosen in the following order: Row Label, Virtual Columns of type Name, Name type columns, key columns, required columns, normal columns in sheet order.

The deck view also has an option to select a layer of data to display as a secondary view. This 'nested view' provides a way to visualize lists of related data created by building references between tables

The nested views can be other tables, decks, galleries or charts - for example, a quick snapshot of a product inventory bar chart for each company displayed in a deck view:

To enable a nested view, app creators can simply look for the 'Nested Table Column' field within the deck view to choose a 'related' list of items. Customize the view type of that related list by finding the corresponding 'inline' ref view that was automatically created when the relationship was created. 

See the Deck view in the Lead Tracking sample app.

See the Table view in the Delivery Tracking sample app.

See the Nested View in a Deck View in the Inventory Management sample app.

Did this answer your question?