Indyco allows you to export and import a Project Dictionary, a file that contains the complete definition of the metadata of a project.

This functionality is available both in indyco Builder and indyco Explorer.


The Project Dictionary is a powerful tool to:

  • Get a comprehensive overview of all project metadata
  • Perform bulk edits on attributes and measures
  • Apply metadata updates consistently across the project by re-importing the modified file


What is a Project Dictionary


A Project Dictionary is an Excel file that includes the metadata definitions of:

  • Attributes
  • Measures

It represents the metadata layer of the project, not its structural model.

The dictionary can be exported, edited externally (for example in Excel), and then imported back into Indyco to apply changes.



Exporting the Project Dictionary


From indyco Builder:

  1. Open a project
  2. Navigate to: Tools > Project Dictionary > Export to Excel
  3. Save the generated Excel file


From indyco Explorer:

  1. Open a project
  2. Navigate to the Dictionary section
  3. Click the Export to Excel button



Editing the Dictionary File


Once exported, the dictionary file can be:

  • Used as documentation to review project metadata
  • Modified to update metadata values for attributes and measures


You can safely:

  • Edit existing rows
  • Remove rows if you want to update only a subset of elements


⚠️ Important

Only the rows present in the imported file will be affected. Any element not included in the file will remain unchanged.



Importing the Project Dictionary


After editing the file, metadata changes can be applied back to the project.


From indyco Builder:

  1. Open the target project
  2. Navigate to: Tools > Project Dictionary > Import from Excel
  3. Select the modified dictionary file and confirm the import


 


Import Process Overview


The Project Dictionary import process is designed to be transparent, controlled and safe.

It is structured into three distinct phases:


1. Excel file analysis and difference detection

The selected Excel file is read and al differences between the file and the current project metadata are identified.


2. Review and selection of changes

A dedicated window is displayed, showing in detail the detected differences.

From this window, users can:

  • Review each proposed change
  • Decide which attribute and measures should be updated
  • Exclude specific elements from the import if needed


3. Execution of the import and optional logging

Once the selection is confirmed:

  • The chosen metadata changes are applied to the project
  • Optionally, a log file can be generated containing the full detail of the imported changes


This step-by-step workflow ensures that no modification is applied without explicit user confirmation.



Supported Columns During Import

During the import process, only specific columns are considered, depending on the element type.


Measures

For elements of type measure, the following columns are processed: 

  • Name
  • Description
  • Note
  • Source Table
  • Source Field
  • Formula
  • Logical Name
  • SQL Type
  • Length
  • Precision
  • Scale
  • Any additional column is treated as a Custom Property.


Attributes

For elements of type attribute, the following columns are processed:

  • Name
  • Description
  • Note
  • Sample Values
  • Source Table
  • Source Field
  • Logical Name
  • SQL Type
  • Length
  • Precision
  • Scale
  • Any additional column is treated as a Custom Property.



Scope and Limitations


Importing a Project Dictionary does not modify the project structure.


You can:

  • Update metadata values of existing elements

You cannot:

  • Add or remove attributes or measures
  • Change relationships or the conceptual model
  • Add or modify custom properties


If your goal is to export and modify the conceptual model structure, refer to the following guide:

→ Exporting an existing model to Excel



Note on Conformed Hierarchies

There is an important behaviour to be aware of when working with conformed hierarchies.

  • The exported dictionary includes all attributes in the project, including those coming from imported conformed dimensions.
  • Each attribute of a conformed dimension appears once for each of its usages, in addition to its original definition.


Metadata Propagation

When importing a dictionary:

  • If a metadata change refers to the definition of an attribute belonging to a conformed dimension
  • That change is automatically propagated to all its usages across the project

This ensures consistency while still allowing centralized management of shared dimensions.