This import wizard makes the configuration process faster, this tool make possible . This tool allows you to set the solution configuration like another '.dbsln' or '.tproj' file with just with a few clicks. The Import Solutions Feature feature is available at Solution → Import Tags → Solution.
When selecting the Import solutionSolution icon, a dialog window will open up with options to customize the import process. The following section will give an explanation of explain the options.
On this page:
| Table of Contents | ||
|---|---|---|
|
Import Settings
Solution | |||
|---|---|---|---|
Solution | The field that allows you to browse for a solution’s path. E.g.: C:\ProgramFiles (x86)\solutions\Mysolution.tproj
| ||
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 Tags 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:
| ||
| Note |
|---|
It is important to remember that once a solution is imported, it can only be manually deleted. There is no automatic delete function. So , be careful before completing this process. |
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|