Versioning a Project

GenericsData Logo GenericsData & HandleData Logo HandleData - Version 9.2.0

Versioning allows a Project to evolve while retaining multiple versions of its elements. Each version can be used, exported, imported or duplicated independently.

For example, the same Project can retain a 1.0 version used by consumers while its 2.0 version is being prepared. Selecting the working version and activating a version are two separate actions.

In summary

Understanding versions

Project Versioning -Versioning concepts
Concept Description

Project

Set of versions grouped under the same identity. The common identifier is used in particular to identify the Project during import.

Project version

Version identified by a unique number within the Project. It has its own elements and description.

Current version or working version

Version currently opened by the user.

Default version

Reference version of the Project in the instance. A Project has only one default version at a time.

Version

Another version of the same Project. Not being the default version does not mean that its elements are unavailable: they can continue to be used and configured.

Settings shared by all versions

The metadata, root code, confidentiality, users (including any manager role), permission template and criticality settings are shared by all versions of the Project. They constitute the settings of its envelope.

These settings are available on the Project edit page. Once saved, any change to them applies immediately to all its versions.

When importing or duplicating a version into an existing Project, the existing envelope settings are retained. They cannot be redefined in the version creation form.

Changing the root code impacts the URL of the DataAPIs for all versions and will therefore cause consumers to lose access to the shared data. This change should be anticipated and handled with caution.

Version number and description

The version number must:

  • contain only groups of digits separated by periods;

  • start and end with a digit;

  • contain no more than 32 characters;

  • be unique among the versions of the same Project.

Valid examples: 1, 1.1, 1.0.0, 1.1.20260909.
Invalid examples: v1, 1., .1, 1..2, 1.0-beta.

The Version field can be edited during duplication or when creating a new Project. During import, it is displayed as read-only.

It can also be edited when creating a New version of an existing Project by duplicating its current version.

The same version cannot be imported more than once into an existing Project. If the version already exists in the Project, its version number is automatically changed by the system.

The Versions tab of the Project configuration allows you to view, edit, manage permissions on elements and delete Project versions in a table.

The available actions on a version depend on the current version, the default version and the status of the version concerned when the tab is opened. An information button displays the details of the conditions for performing these actions on Project versions.

The following matrix provides an at-a-glance overview of which actions are available for each case.

Version displayed in the table Configuration Permission management Set as default Deactivate Reactivate Delete

Current + default

✓

✓

—

—

—

—

Current + not default

✓

✓

✓

—

—

—

Not current + default

—

—

—

—

—

—

Not current + not default + enabled

—

—

✓

✓

—

✓

Not current + not default + disabled

—

—

—

—

✓

✓

Choosing your working version

The version being used is indicated next to the Project name in the DataChain top menu.

  1. Open the list of versions next to the Project name.

  2. Locate the desired version.

  3. Select this version to open its elements.

All versions of a Project are accessible to each of its users.

Selecting a working version does not change the Project’s default version.

Creating a new version

Managing versions requires being a manager of the relevant Project.

Two options are available: duplicate the working version or import a version exported in .dca format.

Duplicating the working version

  1. Open the version of the Project to use as the basis.

  2. In the Project page actions menu, select New version.

  3. Enter a unique version number that complies with the expected format and complete its description (optional).

  4. Configure the other duplication options.

  5. Click Duplicate project: this starts creating a clone of the working version, which will become the new version of the Project.

  6. Once processing is complete, check its configuration.

If the version number is left blank, the system will name the version by appending a hyphen and the number of versions sharing that number in the Project to the working version number.
Example: working version: 1.1; version created by duplication: 1.1-1

The Project’s shared settings are retained automatically.

From the Project page actions menu, New version creates a new version of the same Project by duplicating the current version. Duplicate creates a separate Project. Select the action corresponding to the desired result.

Importing a version of an existing Project

  1. Open the destination Project.

  2. In its actions menu, select Import a version.

  3. Select the .dca file exported from this Project.

  4. Check the displayed version number, the elements to import, the contexts and the member associations.

  5. Click Create project: this creates the Project stored in the .dca file as a new version of the current Project.

  6. Once processing is complete, check the imported elements.

If the version number already exists in the destination Project, the system will rename the version by appending a hyphen and the number of versions sharing that number in the Project.
Example: version already present in the Project: 1.1; renamed version: 1.1-1

The Project contained in the imported file must correspond to the same Project as the destination for the operation to succeed.
A Project with a different Project identifier cannot be imported as a version of this Project.

When an import is started from the Project list and the instance already contains this Project, DataChain offers to import it as a version of the existing Project.

This offer can be declined to create a new independent Project from the file.
A new Project identity is then created.

The general import options are described in Import a Project.

Exporting a version

  1. Open the version of the Project to export.

  2. Check the working version number in the top menu.

  3. Start Export from the Project actions menu.

  4. Select the content of the .dca file, then start the export.

The export applies to the working version. It does not group all versions of the Project and does not necessarily apply to the default version.

The created archive retains the version number of the exported Project version in its data.

See Export a Project for details about the options and download.

Changing the default version

The default version is the one opened when clicking the card of a Project containing multiple versions from the Project list. The DataAPIs of this Project version are those consumed by default by Marketplace users.

Setting a version as default makes it the reference version of the Project and removes this status from the previous default version.

Before this action:

  • check the elements and data of the version to be set as default;

  • initialize or publish, in this version, the DataLinks and DataAPIs and, more generally, the shares consumed in the current default version;

  • identify the DataLink consumers to switch to the future default version and perform the switch;

To set a version as default:

  1. Open the list of Project versions in the top menu.

  2. Use the Set this version as default action (represented by a play icon) associated with the desired reference version.

The default version is identified in this drop-down list by a dedicated icon.

Deleting a version

Deleting a version is permanent and deletes the elements it contains. It requires management permissions for the relevant Project.

  1. Check the DataLinks and DataAPIs still being consumed from this version.

  2. Perform a backup export if necessary.

  3. Open the Versions tab of the Project configuration.

  4. Use the Delete version action on the relevant row.

  5. Check the summary and follow the confirmation steps.

The default version cannot be deleted while the Project has other versions. To delete this version while retaining the Project, first create a new version of the Project and then set it as the new default version.

To delete the last version of a Project, delete the Project in its entirety, as described in the project management documentation.

Versions are deleted individually. For a critical Project, also follow the validation process using the code received by email.

Deleting a version containing DataLinks may deprive consumer repositories of other Projects of their source. Before deleting the version, check whether its shared elements have consumers.

Dernière mise à jour le 28 octobre 2026 à 18:35