This import wizard makes the configuration process faster. This tool allows you to set the solution configuration like another '.dbsln' or '.tproj' file with just a few clicks. The Import Solutions feature is available at Solution → / Import Tags → / Solution.
When selecting the Import Solution icon, a dialog window will open with options to customize the import process. The following section will explain the options.
On this page:
| Table of Contents | ||
|---|---|---|
|
Tutorial
The tutorial in the image below shows how to import configuration from Solutions.
Import Settings
Solution
Solution
The field that allows you to browse for a solution’s path. E.g.:
C:\ProgramFiles (x86)\solutions\Mysolution.tproj
| Info |
|---|
solutions (extension .tproj) and Components (extension .tcomponent) are supported in this feature. |
Preview
The user gets a chance to verify all objects available in the Source solution before importing it to the Target solution.
Concatenate contents on Script Classes with the same name
If there is a Class with the same name in both solutions, the contents from the Class in the Source solution are going to be appended to the class in the Target solution.
If there are methods with the same name in both classes, the method will appear twice after the import if completed.
Concatenate contents on Script Tasks with common names
If there is a Task with the same name in both solutions, the contents from the Task in the Source solution are going to be appended to the task in the Target solution.
Append members on UserTypes with same names
If a UserType Template (created on Unified Namespace → Data Templates) with the same name is found in both the Target and the Source solutions, the members from the latter are appended to the first.
Skip predefined pages (About, Header, LogOn and SelectPage)
If this CheckBox is selected, the default pages are not imported with the rest of the solution.
This is useful if your solutions already share the same header and the other pages (custom or default ones). Skipping these displays will reduce the time it takes to import.
On duplicated objects
This defines what the procedure will be for elements that are found in both solutions (Source and Target).
The options available are:
Skip: objects from the Source solutionare ignored and objects from the Target solution are keptRename: objects from the Source solution are imported and renamed (<OriginalName>2)
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|