> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/the-portal/data-hub.md).

# Data Hub

Reference for the Data Hub, the panel where you find ServiceNow records and drag them into your Command content.

The Data Hub is where records come from. It lists the tables you are allowed to read, lets you find records in them, and lets you drag those records into whatever you are building. What arrives in your content is a pointer to the record, never a copy.

## What it is

A panel that opens beside the work area. It shows records in two sections:

| Section           | Holds                                                                                                                                                                                                   |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Current state** | Records that exist in your ServiceNow instance now.                                                                                                                                                     |
| **Future state**  | Records that are planned but not built yet, held separately so planning never overwrites live data. See [Future State Repository](https://docs.ins-pi.com/command/features/future-state-repository.md). |

Each section shows its own count and can be collapsed. Its header has **Add all**, **New** and a **⋯** menu with **Add to…**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-f82b530356f347d6279de0f7ef135fb22b940bd6%2Fcommand-datahub-open.png?alt=media" alt="The Data Hub open beside a Roadmap, with Business Application chosen, the Search box, and the Current state and Future state sections listing records you can drag in."><figcaption><p>The Data Hub with its Current state and Future state sections</p></figcaption></figure>

## When to use it

Almost every piece of content starts here. Open the Data Hub to find the applications, capabilities or ideas you care about, then drag them onto a roadmap, a map, an analysis or a table.

## How to

### Find records

1. Click **Data Hub** at the bottom of the activity rail, or press **⌥D** (**Alt+D**). The entry appears when the item in front of you can take records.
2. Click **Select table** and type in **Find a table**. Use **↑** and **↓** to move through the tables and **Enter** to choose one. Star the tables you use often, with a click or with **→** and **Enter**.
3. Search within the table with **Search**, sort it (**Name A-Z**, **Name Z-A**, **Recently added**, **Oldest first**), or open the **Filters** funnel to build conditions. Filters apply to current-state records only.

Records arrive a page at a time. Click **Load more** at the end of the list for the next page; while it loads, it reads **Loading records…**. The table list works the same way with **Load more tables**.

When a Relationship Editor is open, the table list shows only tables related to its record; click **Show all** to see every table.

### Put records into content

1. Drag a row, a selection, or a whole section header onto your content. While you drag, only the places that take the drop light up; a place that refuses stays dark and says why.
2. Hold **Shift** while dragging to bring a record's children too.
3. Click the **+** on a row to add it, or on a class row to add the whole class. The **+** spins until the record has arrived. On a row already added, **+** adds whatever underneath is still missing.

Without dragging, use **Add to…** on a row's **⋯** menu, search for the place and pick it. **Add with everything underneath to…** brings the children too.

Records already in your content are marked as added. A Table or Roadmap shows a preview of what a drop would add before you let go. The Data Hub reads at most 10,000 records at once; narrow the filter for more.

### Create a current-state record

1. Select the table and click **New** in the **Current state** section. The button is there only when your ServiceNow roles let you create records in that table.
2. A [Form](https://docs.ins-pi.com/command/the-portal/content-types.md#form) opens for the new record, ready to fill in. Fields the record needs are marked as required. A required field the table's form does not show appears under **Required to create**.
3. Click **Save**. The record is created in your ServiceNow instance, and the form changes into that record's normal form.

If a field could not be set, Command names it: either the record is created without it, or nothing is saved and the message says which fields your access does not let you set.

If Save says **Creating records needs the latest server update**, your instance does not have the server update that creates records yet. Ask your administrator to install it.

### Create a future-state record

1. Click **New** in the **Future state** section. A form opens for the planned record.
2. Fill it in, including a **Name**, and click **Save**.
3. Place it on a roadmap or a map next to the real records.

To abandon a future record you no longer need, choose **Abandon** from its **⋯** menu, or press **Delete** on its row, and confirm with **Abandon**. Creating, duplicating and abandoning planned records needs the Command editor role.

### Open a record

Use a row's **⋯ > Open record** to open the record as a [Form](https://docs.ins-pi.com/command/the-portal/content-types.md#form). Double-clicking a row adds it to the content in front of you instead. Saving writes to the real record, and everything else that points at it picks up the change.

## Good to know

* **Permissions apply.** Only tables your ServiceNow roles let you read are offered. A table you cannot read says why instead of showing zero, for example that you have no access, or that the application owning it does not let Command read it. Creating a record follows the same rules: a field you are not allowed to set is not written, and Save tells you which ones.
* **Class groups.** Where a table has extensions, records are grouped by class, for example Business Application under Configuration Item. You cannot drag a class group onto a canvas, but its **+** adds everything in it.
* **Hierarchies.** Records that form a parent and child structure are shown as an expandable tree.
* **Counts stay consistent.** The selected table in the picker shows the same counts as the sections. When a search or filter narrows the current state, its header says "filtered".
* **One record, many places.** The same record can be in as many pieces of content as you like. Removing it from one does not touch the record.
* **With the keyboard.** Each section's records are one Tab stop. Use the arrow keys, **Home**, **End** or a typed letter to move, **→** and **←** to open and close a row. **Enter** adds the record, **Shift+Enter** adds it with everything underneath, and **Shift+F10** opens its menu.
* **On a ServiceNow form.** Where a Command view such as the relationship view is part of a ServiceNow form, the Data Hub opens from a narrow **Data Hub** rail at its edge. There, **Open record** opens the record in a new browser tab.
* **On a phone** the Data Hub covers the screen and never opens by itself. Close it with **Close Data Hub**.

## Related

* [The Portal](https://docs.ins-pi.com/command/the-portal/portal.md)
* [Content types](https://docs.ins-pi.com/command/the-portal/content-types.md)
* [Access Rights](https://docs.ins-pi.com/command/prior-v26.0/configuration/access-rights.md)
* [Metamodel](https://docs.ins-pi.com/command/reference/metamodel.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/command/the-portal/data-hub.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
