Models in QPR Metrics are saved in the QPR Metrics Server's database. Once a model has been exported to file format, then it can be easily handled like any other file, i.e. saved to disk, attached to an e-mail, etc.
With the merge models function you can merge two models into one model. This operation can only be performed by a user with Administrative rights and when there are no other users connected to the QPR Metrics Server. The Merge option can be found in the Application menu: Manage Merge.
When you merge two models, the elements' ids, i.e. elements' identifiers, are recreated. This is done to avoid conflicts with existing elements. As long as there are no conflicts, the element identifiers remain. If an identifier is found in the model, the element is assigned a new identifier ('MEA' + id). User information such as roles are left empty in new elements.
To merge two models into one, do the following:
|1.||From the Application menu, select Manage > Merge.|
|2.||The Select an import file window opens. Here you must select from file models listed, the first of the two models to be merged. File models are models that are not currently in the QPR Metrics database. File models have the *.qprmem file extension. Once you have selected the model, click Open.|
|3.||Next the Merge Model window opens. From the list of server models, select the second of the two models to be merged. Server models are models that are currently available in the QPR Metrics. This model and the model selected in step 2 will be merged and the result will be placed in the server model that you selected in this step.|
|4.||Click Merge. A progress indicator is displayed until the models have been merged. An information dialog will appear reporting if the merging was successful or not. If the merging was successful, then any changes made during the merging process are presented. If the merging was not successful, then the reason is presented.|
|5.||The currently open model now contains the data of two merged models.|
Note: Models must have matching period systems, otherwise the models cannot be merged. A matching period system contains the same amount of period levels and an identical hierarchy. If the file model contains a period that does not exist in the database model, merging will not work. On the other hand, the database model can contain periods that do not exist in the file model. As long as the file model's periods exist in the database model, the merge will be performed.
When merging models, their views are merged, too, so that the resulting model will have the views of both models. For more information on views see Configuring the Hierarchy Views and Configuring the Dashboards view.