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

# Review entity details

> Understand an entity's metadata, columns, sample data, SQL, and available actions.

An entity detail page explains what an entity contains, where it comes from, and whether you can query or manage it.

## Read the header

The header shows the entity name and its current state. A published entity displays an enabled or disabled indicator. An unpublished entity displays **Draft**.

Review these fields before using the entity:

* **Version** identifies the entity version you are viewing.
* **Type** distinguishes a blueprint, transformation, or imported entity.
* **Status** shows whether a version is live or moving through deployment.
* **Query access** indicates whether your role can query the data.
* **Source**, **Created**, **Created By**, and **Tags** provide ownership and discovery context when available.

<Note>
  Query access and management access are separate. You may be able to inspect an entity without
  being able to query, edit, publish, snapshot, or export it.
</Note>

## Review the content

Use the section navigation to move through the page.

### Description

Read the entity's intended purpose and any usage guidance. Treat a missing or ambiguous description as a signal to confirm the entity with its owner before building a critical report.

### Columns

Search columns by name, data type, description, or constraint. The table can show constraints such as required, primary key, foreign key, unique, allowed values, or PII.

Column labels describe the schema. Your role still determines whether DataX returns the underlying values.

### Sample data

Use sample rows to confirm shape and representative values. Samples can be unavailable when the entity has no data, your role cannot query it, or the sample request fails.

### SQL

Blueprints and transformations can include a **SQL** section. Use **Copy SQL** when you need the definition in a worksheet. Imported entities may not expose SQL.

The page can also list upstream dependencies and downstream entities. Select a dependency to open its detail page.

## Use entity actions

Open **More actions** to see the actions available for the entity and your role.

* **Explore** shows high-level connections.
* **Relationships** shows column-level joins and cardinality.
* **Lineage** shows the transformation flow.
* **Version Control** compares published and historical versions.
* **Copy** starts a copy workflow when available. Use **Copy SQL** to copy SQL text.
* **Export** requires scheduled-export management access; **Snapshot** requires snapshot management access. Both require an enabled, published blueprint that you can query.
* **Enable** or **Disable** changes whether a published entity is available.
* **Delete** removes a supported client-managed entity after confirmation.

Editable entities also show **Edit**. If a newer draft exists, use **Edit Draft** to continue that version instead of creating a competing change.

<Warning>
  Disabling or deleting an entity can affect worksheets, dashboards, reports, exports, and
  downstream entities. Review [lineage](/datax/catalog/lineage) before making the change.
</Warning>

Learn how to [edit and publish a blueprint](/datax/catalog/edit-and-publish-a-blueprint) or [compare blueprint versions](/datax/catalog/blueprint-versions).

## Review and change refresh latency

Where available, **Latency** shows the configured refresh lag and **Last refresh** shows the most recent refresh recorded for the entity. Latency is a configuration value; it does not guarantee that upstream data has arrived.

With blueprint management access, open the entity's menu in **Source explorer** and select **Edit Latency**. The entity must be enabled.

1. Review **Current Latency** and **Upstream entities**.
2. Enter a positive whole number in **New latency**, then choose **Unit**.
3. Resolve any dependency validation message shown in the dialog.
4. Select **Update** and confirm the updated latency in the entity details.