> ## Documentation Index
> Fetch the complete documentation index at: https://doc.qbilon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating Tables

> Create a table view and configure its data selection.

A new table view can be created by clicking on the "`+`" button at the top of the Tables List in the `Custom Views` section.

## Define Rows (Asset Types)

In the first step, specific asset/relation types for the table view can be selected, e.g. "Azure Virtual Machines" or "Azure Disks". In the resulting table view, each single row will show an instance of the selected asset/relation types together with their properties.

![Creating Tables: Define Rows (Asset Types)](https://mintcdn.com/qbilon-docs/aJQhbcvq7mtvhV0w/.gitbook/assets/0af5bb0a-f4b4-4e6f-83be-0af59f2f986c-screenshot-2026-10-08-143852.png?fit=max\&auto=format\&n=aJQhbcvq7mtvhV0w\&q=85\&s=a60e870e16f22aaf0413b46a48f77431)

The first step is selecting the asset/relation types to be shown by the table view.

## Constraints & Analysis Rules (Coloring)

It is also possible to optionally define constraints and analysis rules for the selected asset/relation types.

![Creating Tables: Constraints & Analysis Rules (Coloring)](https://mintcdn.com/qbilon-docs/lr-P4KF_9wn8x9Vs/.gitbook/assets/c207fc69-1687-4837-b7b0-84b9163592b3-screenshot-2026-10-08-144005.png?fit=max\&auto=format\&n=lr-P4KF_9wn8x9Vs\&q=85\&s=bb7343f1c7b32b362227313ed996a7c8)

Defining Constraints and Analysis rules for a specific asset/relation type is possible by clicking on the "pencil" icon on the right.

**Constraints** show only asset/relation instances that fulfill the constraints. **Analysis Rules (color rules)** define under which conditions asset/relation instances are shown in certain colors.

They can be created by clicking the edit button (pencil icon) next to the selected type. In the appearing menu, constraints and analysis rules (coloring) can be added via the `+ Add Constraint` and `+ Add Rule` buttons. Using the operators (`AND`/`OR`), multiple conditions for one constraint or analysis rule can be defined.

![Creating Tables: Constraints & Analysis Rules (Coloring)](https://mintcdn.com/qbilon-docs/Jmla3tEw4FRYjkNT/.gitbook/assets/5d7bfea5-b6af-4431-8798-308600027f1f-screenshot-2026-10-08-150939.png?fit=max\&auto=format\&n=Jmla3tEw4FRYjkNT\&q=85\&s=ca89a0c769d82c0acf59b1b439a5fa43)

Example for a constraint defined for "Virtual Machines" instances.

## Define Columns (Properties & Relations)

In the next step, the properties to be shown for each asset/relation are selectable, e.g. the "Name" and "Power State" of each "Virtual Machine" instance.

![Creating Tables: Define Columns (Properties & Relations)](https://mintcdn.com/qbilon-docs/aJQhbcvq7mtvhV0w/.gitbook/assets/02130577-6ca9-4f4f-9361-7a79e5c9bc4f-screenshot-2026-10-08-151224.png?fit=max\&auto=format\&n=aJQhbcvq7mtvhV0w\&q=85\&s=ee361d0000ae071ec77625090eb9ae07)

Column Definition Example

A column can either refer to ...

* properties directly belonging to an asset/relation – such as "Name", "First Seen" or "Power State" – or
* relations associated with that asset/relation (see figure below).

![Creating Tables: Define Columns (Properties & Relations)](https://mintcdn.com/qbilon-docs/Jmla3tEw4FRYjkNT/.gitbook/assets/bb435818-8ba9-4a6a-bc00-54fe99e2154e-screenshot-2026-07-29-145426.png?fit=max\&auto=format\&n=Jmla3tEw4FRYjkNT\&q=85\&s=4b34a2551fafe6a1f392b18fc28c1b4d)

Example for additionally showing properties of "neighbors" of "VMs" via its dependencies to "Servers". In this case, the column shows the name of the server that a virtual machine is running on.

Using "relations" in tables is a powerful feature, as it can deliver information which is not directly retrievable from the initially selected "types":

* Using relations **as property of asset types**:

When a table view is defined for the asset type "Virtual Machine", the assignment of virtual machine instances to certain "Servers" can be displayed via adding the relation "hosted\_on \[VM→ Server]" as column as shown above.

* Using relations **directly as "type"** in the initial "Define Row Entries" step (see above):

When a table view is defined for the **relation type** "hosted\_on \[VM→Server]", using its "Source Asset Properties" and "Target Asset Properties" can quickly deliver a list of all VMs together with the servers their running on.

## Table View Summary

In the "Summary" step, the final data schema of the table view is shown. As a last step, a name and an optional description for the view can be defined.

![Creating Tables: Table View Summary](https://mintcdn.com/qbilon-docs/lr-P4KF_9wn8x9Vs/.gitbook/assets/e49b3e25-2cc9-498a-8c82-b45bda62bec4-screenshot-2026-10-08-151312.png?fit=max\&auto=format\&n=lr-P4KF_9wn8x9Vs\&q=85\&s=f0e8d98cfc342129f9c40f887ec10e1c)

Table View Summary Example


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.