> For the complete documentation index, see [llms.txt](https://help.holixa.com/holixa-erp-connector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.holixa.com/holixa-erp-connector/data-interface-reference-manual/erp-data-displayed-dynamically-in-ve-tab.md).

# ERP data displayed dynamically in VE Tab

Vault Explorer UI can be extended to show Tab with detailed information. This data is not stored as Vault entity property values – it is just displayed within the Tab of the Vault entity in Vault Explorer UI.

This data is provided by SQL view defined in the same SQL database as DI. SQL view can be created for every EcEntityType.

These two rules must be strictly followed:

1. the name for the SQL view:
   1. pattern: EcTAB\_\<VaultEntityClassId>
   2. examples: EcTAB\_ITEM EcTAB\_CUSTENT\_1

(mind the suffix - custom entity definiton id)

1. SQL view must contain column “name” (nvarchar)

this column is used to select the proper data to display in the Tab

it means the “name” column in the SQL view contains values responding to the Vault entity names (ITEM number , FLDR name, CUSTENT name, CO number)

Tab displays all the fields defined in the SQL view – example:

<table data-header-hidden><thead><tr><th></th><th></th><th width="150"></th><th></th></tr></thead><tbody><tr><td><strong>name</strong></td><td><strong>stock_location</strong></td><td><strong>stock_quantity</strong></td><td><strong>price</strong></td></tr><tr><td>12-3456</td><td>Prague</td><td>1200</td><td>2,45</td></tr><tr><td>12-3456</td><td>Munich</td><td>30</td><td>2,68</td></tr><tr><td>12-8811</td><td>Prague</td><td>300</td><td>102,36</td></tr></tbody></table>

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

trailing spaces in name column are ignored
{% endhint %}

####


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.holixa.com/holixa-erp-connector/data-interface-reference-manual/erp-data-displayed-dynamically-in-ve-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.