DIQ_VariableFolder
Overview
The
It allows variables to be grouped using a tree-based folder structure, making them easier to navigate, manage, and search within DimensionIQ and the host application.
Folders may contain child folders, allowing nested structures such as a/b/c to be created using the
Unlike constants, which are global and available across all projects, variables belong to a specific
The host application is responsible for persisting
Properties
| Property | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Unique identifier for the variable folder |
parentFolderKey | string | Yes | References the parent DIQ_VariableFolder and defines the folder hierarchy |
projectKey | string | Yes | References the DIQ_Project that owns this folder hierarchy |
name | string | Yes | Display name of the folder |
Implementation Guidelines
Data Persistence
The host application should not create or modify folder metadata. When a new folder is received it should be persisted, and when an updated folder is received the existing record should be updated using the values supplied by DimensionIQ.
Folder Hierarchy
The
The host application should preserve these relationships exactly as provided by DimensionIQ to ensure the hierarchy remains consistent.
Project Relationship
The
Because variables are project specific, each project maintains its own independent folder structure. This differs from
Variable Organization
The host application may use the folder hierarchy for browsing, filtering, and searching variables but should not modify the structure managed by DimensionIQ.
Read-Only Behavior
All
The host application may read and use stored folder information but should not modify:
- The identifier - key
- The parent relationship - parentFolderKey
- The associated project - projectKey
- The folder name - name
Any changes to variable folders should be performed through DimensionIQ, which will provide the updated