# View Relationship as Table

The View Relationship as Table feature allows users to instantly switch from the visual hierarchy of the Tree View to a structured table format for any relationship node. This empowers users to analyze related records—such as contacts, accounts, cases, or opportunities—in a familiar grid-style layout without leaving the Tree View interface.

With a single click on View as Table, users can view details like full name, email, company, business phone, and related contact in a sortable, searchable tabular view. This provides an ideal balance between visual relationship mapping and analytical list-based insights.

As shown in the screenshots:

* Clicking View as Table under the Contact(1:N) relationship opens a clean table showing all related contact records.
* Users can scroll, filter, and search directly within the table.

This feature significantly improves data exploration efficiency, especially when reviewing large sets of related records. 

<div data-with-frame="true"><figure><img src="/files/Q74bXYtUdulRnSaM4UYY" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/BVT9b55IfzTM6vw856XS" alt=""><figcaption></figcaption></figure></div>

Key Benefits

* Switch between visual and analytical views instantly
* Explore detailed record lists without navigating away
* Search, sort, and scan related records in a grid format
* Ideal for sales, account management, and customer service teams
* Enhances productivity by reducing navigation steps

{% hint style="success" %}
&#x20;For further queries, reach out to us at <crm@inogic.com>
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inogic.com/map-my-relationships/features/tree-view-visualization/view-relationship-as-table.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.