---
title: "Data Model Dependencies"
slug: "data-model-dependencies"
tags: ["applications"]
status: "update"
updated: 2026-10-13T15:32:38Z
published: 2026-10-13T15:32:38Z
canonical: "docs.unqork.io/data-model-dependencies"
---

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

# Data Model Dependencies

> [!WARNING]
> This article requires UI verification before publication. The server supports data model dependency management as a distinct feature from application-type dependencies. Confirm the Creator-facing UI surface in develop before publishing this article.

In addition to application dependencies, versioned applications can depend on specific versions of data models from other applications. A data model dependency ensures that the application references a known, versioned schema rather than a live draft that might change unexpectedly.

## How Data Model Dependencies Differ From Application Dependencies

[Application Dependencies](/unqorkai/docs/application-dependencies) link one versioned application to a specific version of another versioned application. Data model dependencies link an application to a specific data model schema version within a dependency.

Both types are managed from the Dependencies page, but they appear as separate entries.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-07-17 | Draft — pending UI verification before publication. |

The UI (user interface) is a device's end-user interaction and communication point. It can include display screens, keyboards, and mouse. It is also how a user interacts with your application.

A functionality of a software. For example, Copy and Paste is a feature of a computer's operating system.

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

Schema is a declarative language that defines the structure, content, and constraints of the data.