---
title: "Dynamic Views"
slug: "dynamic-views"
updated: 2026-03-09T17:37:17Z
published: 2026-03-09T17:37:17Z
---

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

# Dynamic Views

**Dynamic views** package Slate data in a way that's more accessible to external tools, such as Tableau, PowerBI, and data warehouses.

They are distinct from [materialized views](/v1/docs/materialized-views) in that they reflect data in real time.

## How they work

A dynamic view is a virtual table created from the result-set of a query.

Slate generates this result-set **in real time** every time the view is referenced—hence *dynamic*.

The view is stored in random access memory, consuming computational resources—but not space—in your database.

## When to use them

Dynamic views should be:

- Simple
- Called infrequently
- Contain very few formulas or calculated fields

If your exported data are formula-intensive, complicated, or need to be referenced frequently, [make a materialized view instead](/v1/docs/materialized-views).

## Advantages over regular queries

Dynamic views are **more efficient**for exported data because they reference only those columns specific to the export.

Regular queries retrieve data from multiple tables across your Slate database. Each table that the query references contains more columns than are relevant.

[![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/360037630231.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/360037630231.png)

## Creating a dynamic view

> [!CAUTION]
> 🔔 Important!
> 
> The view **must** have a name unique among other tables in your database. This includes standard tables such as *person* and any custom datasets or entities.

To create a dynamic view:

1. From the main navigation, select **Queries / Reports**.
2. Click **New Query.**A pop-up appears.
3. Enter a **computer-friendly name:**No spaces, no special characters except for underscores.

[![New Query.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/18265447799067.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/18265447799067.png)

1. Add exports and filters as desired. These exports are the basis of a custom table upon which queries can later be run.
2. From the **Edit Query** page, select **Schedule Export**. A pop-up appears.
3. Configure the following settings:

[![Schedule Export.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/18265490800283.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/18265490800283.png)

> [!CAUTION]
> **🔔 Important!**
> 
> The name entered here must match the computer-friendly name of your query *exactly*.
  - **Destination**: View (Dynamic)
  - **View**: Enter the name of the query following view://

1. Click **Save**.

The view is created as a table in the build schema and follows the naming convention `build.[queryname]`.

## Querying on a dynamic view

> [!NOTE]
> 🔑 To access the dynamic view table with a direct SQL connection, users must have the **Direct SQL Access** and **Query** [permissions](/v1/docs/user-access).

Once the dynamic view has been created, the snapshot data is stored on a table (as defined in the **Schedule Export** settings) in the database.

This table can be referenced via direct SQL access, or by Custom SQL snippet parts in a standard query in Slate:

```sql
select [Name], [Event Name] from build.[queryname]
```