Clearion Web - Projects Merge

How configuration changes are delivered across projects in a workspace »

When working with multiple Projects inside one workspace, it’s common to maintain the same configuration across them — pages, widgets, business logic — while connecting each project to different data sources.

For example:

• one project may be connected to test data

• another project to production data

This creates a hierarchy among the projects. Typically, the standard hierarchy looks like this:

Dev projects → Test project → Prod project

Alongside projects, every workspace also contains Groups.

Groups store and organize all workspace entities, including:

• lookups

• themes

• pictures

• data sources

• custom actions, etc.

Each Group is linked to a project, and the hierarchy of Groups mirrors the hierarchy of projects.

For instance:

• the Dev Group contains all entities related to the Dev project

• the Prod Group contains all entities related to the Prod project

Most configuration changes start at the lowest level of the hierarchy (Dev).

These changes can include:

• creating new entities

• updating configuration

Once implemented, changes are delivered upward through the hierarchy: from Dev → to Test → to Prod.

⚠️ During this process, only the configuration is delivered. The actual data in the groups is not overwritten.

To transfer changes from one project to another, two steps must be performed:

1. Groups merge – merges group data across hierarchy levels. This does not override the actual data in DB, this adds new entities to the next group. E.g. a new lookup.

   1. Open the Groups page

   2. Select a Group (e.g. Test)

   3. Click ‘Merge Group‘

   4. Select a recipient Group (e.g. Prod)

   5. Click ‘Save‘

   6. See a success pop-up

2. Projects merge – merges the configuration between projects

   1. Open the Projects page

   2. Select a project (e.g. Test)

   3. Click ‘Merge‘

   4. Select a recipient Project (e.g. Prod)

   5. Click ‘Save‘

   6. See a success pop-up

⚠️ All manual changes must be made at the lowest level in the hierarchy (Dev).

• This ensures that they can be safely delivered to higher levels.

• When a merge happens, the configuration from the lower project fully replaces the configuration in the higher one.

  • Example: if changes are made in the Dev project and merged into the Prod project, the Dev configuration will completely overwrite the Prod configuration.

  • Any manual edits done directly in Prod will be lost.

This is why work should always be done at the lowest hierarchy level and then promoted upward.

⚠️Links set up in the configuration are not replaced during the merge.

Some widgets include links in their configuration.

Widgets that contain links:

• PowerBI widget

• FME widget

• Superset widget

This means links set up in these widgets remain intact, even when the configuration is merged across projects.

Therefore, editing links is the only type of manual change that can be safely done in any project, regardless of the hierarchy.