This article covers the following topics:
This App has the functionality onboard in order to split a project into 1 or more project parts, that can be processed independently of one another. These parts can after completion of the tasks based on these individual parts be merged again into one project. Project merge is actually possible from any project, i.e. from projects that are not the result of a split action. The original intention is however to make splits from a 'master' project and to merge them back afterwards.
A license for this App is only required for the actual splitting and merging of projects. For the editing of the project parts, an ETS license is sufficient.
A project can only serve as a master project if it contains elements that can be split, like e.g. lines in the topology.
Follow these instructions in order to activate this app in ETS:
- Purchase a Split & Merge license from MyKNX
- License it as explained here
- No additional *.etsapp file needs to be installed
Use of the Split & Merge app in ETS
- Open the master project.
- Select the element(s) within the master project to be split
- Distribute the split project(s): export the split and/or the master project(s) via the standard project export mechanism.
The splitting and merging functions are only available when the App is licensed.
Common behavior during splitting & merging of projects
- The master and the split project have no explicit (technical) relation, i.e. they are actually a kind of copy from one another. They 'only' have an (implicit) logical relation based on the project name, which even can changed afterwards.
- When a master or a split project is copied, all split information is copied as well.
- If there are project files or device certificates present in the master project, then they are also transferred into the split project. When merging projects, any project file or device certificate in the split project is integrated into the master project according to the following rules:
- For files with a unique name: they will be integrated
- For files with the same name:
- If their content is identical: they will not be integrated
- If their content is not identical: they will be integrated
- Project properties are always inherited from the master. However, for project passwords, the following applies:
- Merging a split project back with its master, results in a project being protected with the password of the master project.
- Any other merging constellation, results in a project being protected with the password of the first selected project.
- The project split and merge actions can also be logged via the Project Tracing App.