Difference between revisions of "HowTo:Transfer Data from UBIK 3 to UBIK 4"

Save all meta definitions to a SmartStudio Project

• Open SmartStudio version 3.7.
• Open a new, empty Project.
• Connect to the old UBIK^® 3.7 Environment.
• Open a new Transport Container worksheet.
• Right-click to open the context menu and click "Load all MetaClasses".

=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.

• After loading all the meta definitions is finished, save the Transport Container to the Project.
• Save the Project to the file system.

Create an empty UBIK^® 4.0 database

• Create a new, empty database for your UBIK^® 4.0 Environment. It has to be on the same server as your old database (or a copy thereof).
• Open SmartStudio version 4.0.
• Open the previously created Project.
• Connect to the new (and empty) UBIK^® 4.0 Environment.

=> SmartStudio now asks you to upgrade the empty database to version 4.0. Confirm the upgrade dialog. UBIK^® now creates all the basic system definitions in the previously empty database.

=> You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client

Transfer the previously copied meta definitions

• Open the Transport Container with all the 3.7 meta definitions from the Project.
• Merge & Save the Transport Container to the Environment.

=> All the meta definitions should be available in the new UBIK^® 4.0 Environment. Now we just have to transfer the instance data.

Remove obsolete MetaClasses

• Some old meta classes have been transferred, but we can just delete them:
  • System.Main.SYSTEMSETTINGS

Make sure all languages are configured

• Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
• Enter all required languages (if you had more than 2).
• It is only important that there are enough languages, you can modify them afterwards.

=> Now, there should be as many languages as there were in the old 3.7 Environment.

Transfer all instance data

• Open the "Instance Data Transfer Wizard" using the "Environment" menu.
• Follow the wizard's instructions until the end.

=> The wizard copies all the instance data from the old 3.7 Environment to the new 4.7 Environment.

Maintain languages

• All languages have been transferred from the old 3.7 Environment.
• Now, there might be duplicate entries.
• Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.

=> Now, all translations should be displayed correctly; please check.

Optional: Maintain customizing

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

• Copy your custom code library from your old DB to the new one.
• If a class cannot be found, please make sure it doesn't have the namespace "System".

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

• For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
• The method View.Children now doesn't have the parameters "bool sorted" and "bool fullBranchSync" anymore; they can be removed.
• There is a new method View.ChildrenForBranchSync with the same parameters as View.Children (equivalent to having the "fullBranchSync" parameter on true). If you customized View.Children, this one should be customized as well.
• The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

Optional: Maintain system object customizing

Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.

• In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
• Custom property values or relations must be amended manually.
• Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
• Ask a developer if you need help.