Skip to main content

DataTableV2

The DataTableV2 is a component for building tables which organize information into rows and columns.

Visual configuration

The DataTableV2 allows configuration for its visual look, data density, and data point separation to ensure a clear and functional presentation of the data.

Contained and uncontained variants

Contained

  • Use the contained variant for most cases, mainly when it plays a prominent role in the visual hierarchy of the view.

An example of a DataTableV2 component with the contained setting.

An example of a DataTableV2 component with the contained setting.

Uncontained

  • Always use the uncontained variant when it's the only element inside a Surface.
  • Use for a subtler appearance when the table takes on a secondary hierarchy within its context.

An example of a DataTableV2 component with the uncontained setting.

An example of a DataTableV2 component with the uncontained setting.

Data density

The DataTableV2 comes with three density options that control the standard row height and whitespace in a cell.

Condensed

  • Use the condensed row density to show more information in smaller areas and compact layouts. Consider that cell content might be more challenging to scan and distinguish for users.

An example of a DataTableV2 component with the condensed density setting.

An example of a DataTableV2 component with the condensed density setting.

Default

  • Use the default row density for datasets where users should process and scan the shown information.

An example of a DataTableV2 component with the default density setting.

An example of a DataTableV2 component with the default density setting.

Comfortable

  • Use the comfortable row density if you need to improve readability for tables with visually crowded cell content.

An example of a DataTableV2 component with the comfortable density setting.

An example of a DataTableV2 component with the comfortable density setting.

Data point separation

No separation

  • Use no visual data point separation for simple data sets—for example, a key-value list.

An example of a DataTableV2 component with no visual data point separation.

An example of a DataTableV2 component with no visual data point separation.

Horizontal dividers

  • Use horizontal dividers to highlight the distinction and separation between rows.

An example of a DataTableV2 component with horizontal dividers.

An example of a DataTableV2 component with horizontal dividers.

Zebra stripes

  • Consider using zebra stripes for large datasets where users may want to interact with one or more data points in the view to ensure easier scanning and distinction between rows.

An example of a DataTableV2 component with zebra stripes.

An example of a DataTableV2 component with zebra stripes.

Vertical dividers

  • Use vertical dividers to separate columns, especially when dealing with a relatively large amount of data points.

An example of a DataTableV2 component with vertical dividers.

An example of a DataTableV2 component with vertical dividers.

Combined separation

  • Combine zebra stripes and vertical dividers to establish a structured dataset, ensuring row and column distinction for effective readability.

An example of a DataTableV2 component with zebra stripes and vertical dividers.

An example of a DataTableV2 component with zebra stripes and vertical dividers.

Actions

The DataTableV2 can have actions on table, column, row, selected row(s), and cell level. Place an action on a level depending on the content the action affects.

Table actions

  • Use table actions for operations that affect the entire dataset, such as global sorting, filtering, or exporting.

An example of a DataTableV2 component with table actions.

An example of a DataTableV2 component with table actions.

Column actions

  • Use column actions for operations that affect a specific column, such as sorting or column visibility.

An example of a DataTableV2 component with column actions.

An example of a DataTableV2 component with column actions.

Row actions

  • Use row actions for operations related to specific rows, such as Edit or View details.

An example of a DataTableV2 component with row actions.

An example of a DataTableV2 component with row actions.

Selected row actions

  • Use selected row actions for operations that users can perform on one or multiple selectable rows simultaneously.

An example of a DataTableV2 component with selected row actions.

An example of a DataTableV2 component with selected row actions.

Cell actions

  • Use cell actions for operations related to specific cells, such as Copy to clipboard or other context-specific activities for a particular piece of data.

An example of a DataTableV2 component with cell actions.

An example of a DataTableV2 component with cell actions.

DataTableV2 vs. SimpleTable

All visual parameters are configurable for DataTableV2 and SimpleTable.

DataTableV2

  • Use the DataTableV2 for feature-rich interactions like dynamic manipulation and managing datasets with extensive or complex content like charts.

An example of a DataTableV2 component with an extensive dataset and advanced options.

An example of a DataTableV2 component with an extensive dataset and advanced options.

SimpleTable

  • Use the SimpleTable for a purely visual representation of tabular data, without support for any significant interactivity such as sorting or loading performance like pagination.

An example of a SimpleTable component with a simple dataset.

An example of a SimpleTable component with a simple dataset.

Content guidelines

Table actions

  • For table actions, refer to the button content guidelines. Learn more about Button.

Columns and rows

  • Try to keep column headers to one or two simple words.
  • The column header should be singular when it’s a noun.
  • Keep action names in table columns, rows, and cells, to one to three words and be consistent with other usage in the product. Learn more about Button.

Table data

  • For table data, make sure the data is displayed in a consistent format. Learn more about formatting data.
  • Show an empty state when there’s no data or there’s an error. Learn more about EmptyState.
Still have questions?
Find answers in the Dynatrace Community