Conversion Manager

The conversion manager is a tool allowing for generating a script containing the differences between versions. The script can next be run in a selected profile generated on the basis of a standard profile with enabled tracking changes option. The script will add all the newly added buttons referring to the functionalities implemented in this version.

As in the case of the profile editor, the conversion manager can be started by selecting an appropriate button on the database manager ribbon.

Menu with highlighted Conversion Manager button

 

The conversion manager window contains the following buttons:

[Load] – uploads the profiles stored in a configuration database. The profiles are presented in the form of a tree – the profile, on the basis of which the other profiles were generated, is displayed on the top

[Convert] – creates a script which contains all the buttons available, by default, in the field Target Version

[Open Folder] – opens the location of a generated script

Conversion Manager window

In the Conversion Manager window, there is also information about the profile versions. Start and target versions are the points of reference for the generated scripts.

In the conversion manager, Track Changes option plays an important role. It can be checked while creating a new profile or saving changes made to the profile. Checking this option results in associating the two profiles. The original profile is the parent profile, while its copy, that is a newly generated profile, is the child profile. During conversion of a child profile, a script, which copies all the changes from parent profile to child profile, is generated. That script must be executed manually on configuration database.

Conversion Manager window with the tree of profiles available for the configuration database

When converting profiles, the system uses numbers of configuration database versions. Before starting the conversion of profiles, it is necessary to know the version of configuration database before its conversion. Version can be checked in the database manager in the main menu with the use of button [Check Version] available in Configuration Database button group. Moreover, the table below presents subsequent versions of Comarch ERP Standard system and configuration databases starting from version 5.5.

Comarch ERP Standard versionConfiguration database version
5.55.5.154
5.5.15.5.157
5.5.25.5.182
5.5.35.5.192
5.5.45.5.212
6.06.0.103
6.16.1.37
6.26.2.32
6.36.3.31
2015.07.0136
2015.17.1.14
2015.27.2.32
2015.57.5.36
2015.67.6.9
2015.6.17.6.9
2016.08.0.93
2016.18.1.29
2016.58.5.93
2016.5.58.5.104
2016.5.68.5.104
2017.09.0.57
2017.19.1.14
2017.59.5.86
2017.5.19.5.90
2018.0.110.0.95
2018.110.1.40
2018.1.110.1.41
2018.210.2.6
2018.510.5.49
Note
A profile for which the option Track Changes was not checked during its generation cannot be converted.
Note
Profiles must be obligatorily migrated after migrating Comarch ERP Standard system to a later version. During migration of configuration database, version of only Standard profile is upgraded. All other profiles need to be migrated manually with the use of Conversion Manager.
Note
If upgrade of system involves a big leap between versions, e.g., migration from version 5.5.x or 6.x to 2016.x, the generated converting script contains several tens of thousands of lines. Problems may occur in the SQL service, concerning execution of such large scripts. In such case, it is recommended to divide the script into smaller parts and convert a profile gradually from version to version, by specifying subsequent numbers of versions in fields Start Version and Target Version.

Czy ten artykuł był pomocny?