|Frequently Asked Questions|
Elements of an existing model can be imported into other models. Developers can work simultaneously on the same model; importing the different elements to create a new model. You can also reuse parts of a model; streamlining your work and letting multiple developers work efficiently.
The destination model is the model that you are importing to and the model which is open in the Design Tool.
After the import is complete the new model that was created by importing elements from the source model into the destination model is called the master model.
You import from the source model to the destination model. The source model is selected in the Model Import dialog box.
Model elements are those items that may be imported and comprise entities, attributes, operations, recordsets, recordset fields, tables, table columns, procedures and compound procedures, and model variables.
A referenced element is referenced by another element, but not selected for import. All referenced elements must be resolved, either manually or automatically, before the new model can be deployed. See Import Model Elements for more information on referenced elements.
NOTE: If the option Automatically select referenced elements is selected on the Preferences dialog box, then
_notImported elements do not occur. If this option is cleared, then these replacement elements must be resolved manually.
_notImportedin the preview pane of the Model Import dialog box are not problems. It is not unusual to have elements that you do not want to import.
An element, for example an attribute might reference another element, such as a variable. When the attribute is imported, but the variable isn't, then the referenced element is missing. The import function creates a temporary replacement version of the referenced element. These replacements are marked with the
_notImported suffix and inserted into the destination model.
Since all referenced elements must eventually be resolved before a model can be deployed, after finishing the import, use the Design Tool to modify the attribute you have just imported. Find the reference to the placeholder variable and change it to refer to a "real" variable in your model.
If all the screens you want to model are known in advance, it is beneficial to include the entities that will be duplicated across different models in the base model. This prevents a particular entity from having different names across different models and reduces the size of the model.
Yes. If you import a model that contains an event handler, a reference to it is imported along with the parent element. However, you must manually copy the Java code from the model source
Scripts sub-directory to the corresponding sub-directory in the destination model files.
When you select an element that is already in the destination model the element is replaced. However, you must confirm your decision before the element is overwritten. This option is set on the Import tab of the Preferences Setup dialog box and is selected by default.
By default, all import models are validated in the Host Integrator Validator. A model must successfully validate before it can be deployed.
Options that determine how to work with the Import Model Elements dialog box are set on Settings menu > Preferences > Import. See Model Import Preferences for a description of each option, as well as the default settings.
All of the element's properties in the source model are the same as those in the destination model. For example, if an entity exists in both models and all of the entity's sub-items are also marked with a , you do not have to import this element.