In the Data Mart workspace, you can copy models between Data Marts.
To copy models between Marts:
From the Manage Mart window, select the Copy Model Between Marts link.
You see the Copy Model Between Marts dialog box.In the Copy Model Between Marts dialog box, as shown in Copy Model Between Marts Dialog Box, copy some or all of the fields of one model in the source Mart instance to create, or add fields to, the same model in the target Mart instance.
Select from three drop-downs to select the model to copy and the source and target Marts. These fields must be completed in the following order:First, in Source Data Mart list select the Mart instance where you would find the model to be copied.
Next, in Target Data Mart list, choose the destination of copied components.
Then, in Source Data Mart Model list, indicate which model will be copied, in whole or in part.
After filling in these fields, the Source Model section is filled in with the model extensions and fields of the selected model in the source Mart instance. If that model already exists in the target instance, its extensions and fields appear in the Target Model section. Copy Model Dialog Box with Model to Copy not in Target Mart displays an example of copying a model that does not exist in the target Mart instance. The Target Model window is empty.
Select the fields you want to copy from the source to the target.
The Source Model section of the dialog box contains a line for the selected model at the top. The Extension column contains Default. In this dialog box, every model is considered to have an extension called Default, even if it is a group-level model that cannot have actual extensions.
To select a field to copy from the source to the target, select the check box next to it. If a model field is already in the target, you cannot copy it. Even though it is listed, it does not have a check box next to it, so you cannot select it. You can copy a field only once.
A check box also appears next to each extension. If you select an extension check box, all fields of the extension are automatically selected. If you select the check box next to the model name, all fields of the model will be copied.Click Copy to begin copying the selected fields.
If all fields are copied successfully, a message appears. Click OK.
The Target Model section of the dialog box now displays all copied fields in addition to fields that were in the target model before copying.Click Close to close the Copy Model dialog box.
On this page
| borderColor | #9F9F9F |
|---|---|
| titleColor | #F7F9F9 |
| titleBGColor | #B48436 |
| borderStyle | dashed |
| title | Content on this page: |
| Table of Contents |
|---|
Rules to Copy Fields
The following section describes rules that the system follows while copying models. These rules are based on what happens if you add fields to a model manually, since Copy Model is basically a faster alternative to manual model configuration.
| Anchor | ||||
|---|---|---|---|---|
|
Table Name is the basis for deciding if a model in the source is also in the target. Since the table name cannot be changed for Fund Summary or any detail model, only group models might not be matched between Marts due to a difference in the table names used for them.
Table Name is also the basis for deciding if a model extension in the source model is also in the target model. This only applies to Fund Summary and detail models, which are the only types that can have extensions.
| Anchor | ||||
|---|---|---|---|---|
|
Field Attribute ID is the basis for deciding if a field in the source model is also in the target.
In any Mart instance, a field attribute can be linked to only one Database Column Name (the last column in the two panels of the dialog box) and model field ID. If you try to copy a field from the source where some field attribute ID has a model field ID or database column name already used by a different field attribute in the target Mart, a validation error occurs. You can correct this error in the Validation screen by giving the field with a duplicate name a new field ID or database column name. This eliminates the duplication in the target Mart.
In any Mart instance, a group column name, defined on the Grouping tab of the Model Configuration dialog box, cannot be used by a regular Mart field. This prevents the duplication of column names in a single table, since both group fields and regular fields are table columns. When a group model is copied to another Mart, its group column names are checked to verify that they do not duplicate existing field column names in the target Mart instance. However, they can duplicate other group names, as this will not lead to a conflict in any table.
If an extension you are copying does not exist in the target, the extension is copied to the target along with its fields. In the Fields tab of the Configuration dialog box of the target model, the field extension assignment dropdowns are available for reassignment. This allows you to assign those fields to any extension of the target model, not just their assigned extension in the source model. This way, you can avoid using the source extension altogether. Simply reassign all of the source extension's fields to other model extensions, save the model, and delete the now unused source extension. Once you submit the target model to be built, you can no longer reassign fields to other extensions. Once you submit the target model, extensions, and any assignment of fields to extensions are permanent.
| Anchor | ||||
|---|---|---|---|---|
|
If you copy a group-level model that does not already exist in the target, the information content of the model is copied along with its fields. The following non-field items, if present in the source model, are copied when a group model is copied for the first time:
Entities
Currencies
Filters
Performance dictionary assignment
These items are only copied if the group-level model was not previously present in the target Mart. These items do not copy for non-group models. After a model has been copied to another Mart for the first time, you can only copy new fields to that model.
Group-level model configuration items that are operational instead of informational are not copied: These items include:
Schedule selections for the model
Field Schedules selections
User and business group access settings
| Anchor | ||||
|---|---|---|---|---|
|
When you use the Modify command in the Fields tab of the Model Configuration dialog box, you are changing the Field Attribute ID of a field. Even if you copied the field to another Mart before, the modified field appears as if it were a new field added to the source model. If you want the same Modify to be done in the target model, the best approach is to do that manually.