Data Collections

Data Collections are workspace-level reference datasets that modules and workflows can query at runtime. Use Data Collections to store lookup tables, configuration values, product catalogs, and other reference data that must be shared across multiple applications. This approach avoids hardcoding values into individual modules. Data Collections can also be promoted to the library for use across workspaces. See Shared Elements and Workspace RBAC for the sharing workflow.

What Are Data Collections?

A Data Collection is a structured dataset stored at the workspace level. Each collection defines a schema (field names and types) and stores rows of data that modules can query dynamically through the Query API during runtime.

Data Collections store reference data, which is information that modules read but typically don't modify. Examples include:

• Lookup tables: State abbreviations, country codes, tax rates by region.
• Configuration values: Feature flags, environment-specific settings, approval thresholds.
• Product catalogs: Item names, SKUs, pricing tiers, category mappings.
• Reference lists: Department names, office locations, valid status codes.

Each collection belongs to a specific application and can be queried by modules in that application.

When to Use Data Collections

Use Data Collections to:

• Share reference data across multiple modules without duplicating the dataset in each module.
• Update reference values centrally without modifying module logic or redeploying modules.
• Store lookup tables that modules query at runtime to display user-friendly values or validate input.
• Maintain configuration data that varies by environment or changes independently of module updates.
• Centralize product catalogs or reference lists that multiple applications need to access.

Data Collections work best for datasets that:

• Are read frequently but updated infrequently.
• Contain structured, tabular data with a consistent schema.
• Need to be queried dynamically instead of embedded as static values.

Why Use Data Collections Instead of Other Data Approaches

Data Collections provide a middle ground: structured, queryable, centrally managed reference data that modules can access at runtime without external dependencies.

How to Create a Data Collection

Creators can create a Data Collection from the explorer tree in the Explorer tab.

The explorer tree displays a context menu when Creators right-click an application or select the (ellipsis) icon.

1. In the explorer tree, locate an application.
2. Right-click the application, or select the (ellipsis) icon that displays when hovering over the row.
3. Select Create Data Collection from the menu to open the creation form in a new tab in the Unqork platform.

The workspace and application fields pre-fill with the selected application's values.

Creation Form Fields

Schema Definition

Creators can define the collection's schema in two ways: manually or by uploading a CSV file.

Manual Schema Definition

1. In the schema section, select Add Field to add a row to the schema table.
2. Enter a Field Name for each column in the collection.
3. Select a Field Type from the drop-down: String for text values, Number for numeric values, or Boolean for true/false values.
4. Select Add Field to add additional fields as needed.
5. Select Create Data Collection to create an empty collection with the defined schema.

Creators can add data to the collection after creation by opening the collection's detail view.

CSV Upload

1. In the schema section, select Upload a file instead.
2. Drag and drop a CSV file into the upload area, or select a file. The system uses the first row as column headers (field names).
3. Select Create Data Collection to create the collection with the CSV schema and data.

CSV files must meet the following requirements:

• First row must contain column headers.
• All rows must have the same number of columns.
• Maximum file size: 10 MB.
• Supported encoding: UTF-8.

When Creators upload a CSV file, the Data Collection Name field auto-fills with the file's basename. Creators can edit the name before creating the collection.

To switch back to manual schema definition, select Define schema manually instead.

After Creation

After Creators create a Data Collection, the Unqork platform opens the Data Collection Page in a new tab. From there, Creators can add and edit rows, manage schema fields, configure server-side execution, and export or share the collection. Modules and workflows can query the collection immediately through the Query API.

Sharing a Data Collection to the Library

A workspace Data Collection can be promoted to the library so other workspaces can use it. Once shared, the Data Collection is available in Library Elements. Its (ellipsis) menu now shows Access & Usage instead of Share to Library.

To share a Data Collection, select (ellipsis) next to the Data Collection in the Applications section of the Explorer and select Share to Library. This opens the Access & Usage dialog in share mode, where Creators configure the sharing scope.

For the full sharing workflow, permission requirements, and access management, see Shared Elements and Workspace RBAC.

Note: Shared Data Collections cannot be moved to a different application. Unshare the Data Collection before moving it.