DataLinks

The source must be an Active DataBlock belonging to the current Project and for which the current user has the Sharing permission. Selecting it is mandatory to create a DataLink.

A DataLink can be created from the Project’s DataLink list (accessible from the side menu) or from the edit page of its future source DataBlock.

Once the source has been selected and the DataLink created, it can no longer be modified.

Columns of type words, binary, files and geometry are not supported by DataLinks.

An impact check message warns the user when attempting to disable or delete a column from a DataBlock used as a source in a DataLink.

The source DataBlock can no longer be deleted as long as it is consumed by a DataLink.

The general column settings define the columns of the source DataBlock that will make up the DataLink dataset.

They can be modified at any time.
At least one must be selected to create a DataLink, and this minimum must always be maintained.

Each column must have a unique alias: the "DataLink label".

A DataLink profile defines how a DataLink is shared with one or more Consumer Projects.

A DataLink must contain at least one profile, and this profile must contain at least one column template with at least one column.

It can contain as many filter templates as required (0 or n).

For the same source version of a DataLink, a Consumer Project version is associated with only one profile. However, it can consume several source versions of the same DataLink from different repositories.

A Project can also consume several different DataLinks.

When a DataLink is created, the first profile is preconfigured with a column template containing all DataLink columns.

A column template defines the columns that can be consumed by the Projects associated with its profile. It is required when creating a profile.

A default column template is automatically created in the initial profile when a DataLink is created.

It allows a column configuration to be reused across multiple profiles.

It defines the subset of columns (among the enabled general columns) that will be visible for this profile.

A column template must contain at least one active column.

A profile can contain an optional filter template used to restrict the rows exposed to Consumer Projects.

A filter template allows a row restriction to be reused in one or more profiles.

The filter is created using a filter creation interface with predefined operators.

A filter template must contain at least one condition.

Conditions are combined cumulatively (using logical AND/OR operators) when several rules are configured in the filter template.

A share associates a Consumer Project version with a profile of a specific version of the DataLink’s Project. This profile determines the columns and rows to which the consumer has access.

Each share from a DataLink version to a Consumer Project version may involve one or more repositories of that Consumer Project.

Consumer Projects can be added at any time from the Consumer Projects tab.

The selection list displays:

Adding a Consumer Project to the current DataLink applies to all its versions (existing and future).

To add a Consumer Project:

The added Project is assigned to the DataLink of the current version of the Producer Project.

The table distinguishes the Consumer Project, its version, the DataLink supplying it, and the version of the DataLink’s Project.

When a DataLink is present in several versions of its Project and the "All versions" option is selected on the "Consumer Projects" tab, the same Consumer Project may appear on several rows, particularly when its repositories consume different versions of the source DataLink.

Once added, the share can be modified, removed or disabled (only if it is consumed by at least one repository).
Disabling or removing the share deprives the affected repositories of data without deleting them.

To disable one or more shares, select them and click Disable in the table header. The button does not respond if the selection does not contain any shares that can be disabled.

Likewise, use Enable to reactivate one or more shares.

Information about the share status and whether it is actually being used is also available in the table’s Status column.

By default, the table displays consumers of the current DataLink version. Displaying all versions also makes it possible to identify those consuming another version.

Version switching allows the producer to change the source version of the same DataLink used by a Consumer Project version.

The share is the unit of switching: it associates a Consumer Project version with a DataLink profile in a Producer Project version. A single share may be used by multiple consumer repositories.

Switching reassigns this share to the current DataLink version in the Producer Project. The current version is therefore the target version, while the version used before switching is the original source version.

All repositories in the same Consumer Project version using the same DataLink source version are affected together. By contrast, repositories consuming another source version of that DataLink are not affected by switching this share.

When a producer changes the version assigned to a consumer, members of the Consumer Project are notified by email. When the consumer makes the change from a repository, members of the Producer Project are notified.

When the default version of the Producer Project (from which the source DataLink originates) is changed, consumers whose repositories do not allow automatic assignment receive a notification so that they can decide whether to change their source.

Notifications also report access removal, deletion of the producer version or restoration of access after a producer import. The repositories mentioned in the messages depend on the recipient’s viewing permissions.

Initialization creates the published dataset based on the settings of the created DataLink.

The Initialize action is available when:

Initialization is required to share the data.

If the user does not have sufficient permissions on the source columns, the action is blocked by a consistency check.

An update replaces the published dataset with a new snapshot of the source DataBlock data.

The action is available when:

The update applies to repositories consuming the DataLink current version.

If a DataLink column consumed in a consumer repository is disabled and the DataLink is subsequently updated, the column’s data is set to null in the repository.

The publication status indicates whether subscribed Projects can consume the dataset.

The action is available when

The action is available when

When the DataLink has been initialized, the user can delete the published data.

The action is available only if the dataset exists. After deletion, consumer repositories can no longer consume DataLink data until a new dataset is created by updating the DataLink.

The action is available when:

Deleting a DataLink is permanent.

It results in:

The DataLink can be deleted from the DataLink list or from the edit page of the DataLink to be deleted (see drawer menus).