Merging Data Models

Learn how to merge data models.

By default, data model changes transferred between stations using the Aurea CRM win Communication module or CRM.cockpit overwrite the data model on the target station, see Communicating Data Model Changes. By using different (station) number ranges, you can prevent changes to Industry Solution data models from being overwritten by updated data models, for example. Any changes made to the data model are instead merged with the existing data model on the station.

Requirements:

  • Stations used to maintain data models must always be set as the main office, see Defining a Station.
  • Stations used to maintain data models must use different number ranges and/or station number ranges, see Number Ranges in Aurea CRM and Station Number Ranges.
  • A design data model must be present on the target station.
  • For correct handling of texts, make sure to use different language ranges for Base and Industry Solutions. Texts in languages with IDs>= 100 are not overwritten by the base data model during import.

If these requirements are not met, the data model is overwritten on the target station (default behavior).

Note: Aurea recommends only changing those elements (info areas, fields, catalogs etc.) on the station they were added on or have been assigned to the station’s number range.

Merging data models via e-mail

The data model can be exported, sent via e-mail, and imported on the target station.

  1. Select Export Data Model (-> E-Mail) from the context menu for the Active data model.

    An e-mail is created with the subject "MM_BLOB_2". A file with the same name is added as an attachment.

  2. Send the e-mail.
  3. Select Import Data Model (<- E-mail) from the Design node’s context menu.

    The data model is imported. (The system searches for the corresponding e-mail in the current user’s inbox.)

    Two new archived data models are created on the target station:

    • The newly imported data model (with the corresponding station number)
    • The current design data model on the target station prior to importing the new data model

    Any messages concerning problems that occurred while importing the data model are written to the Maintenance module’s log file, see Logs and Error Messages.

  4. The imported data model changes are color-coded, as with "normal" data model changes, and need to be applied manually, see .

    • yellow: New elements that can be applied to the data model or deleted
    • red: Elements deleted in the external data model. If you apply the changes, the element is also deleted on the target station. If you select Undo Changes from the context menu, the element is retained on the target station.
    • pink: Elements changed by the external data model that were already present in the internal data model. In this case, the element properties are displayed for the data model that the element was originally added to. You can apply the change, undo the change, or change the affected element manually before applying changes.

Merging data models via communication

You can also merge data models using <suite's> communication mechanism. In order to be able to merge data models, the data model you are importing may not have been created on the target station.

When inputting the data model, a message is displayed:

  • Confirm with Yes to merge the data models automatically. Only in the case of conflicts are these changes color-coded and need to be applied manually (see above).
  • Select No to cancel the process with error 45.

Message concerning problems encountered when inputting the data model are written to the Communication module's log file.

Once you have input the data model, you are prompted to restart communication.

In order to merge data models using automatic communication, use the --DmMerge parameter, >> mmco.exe Parameters.

Merging data models via CRM.cockpit

Merging data models in CRM.cockpit is identical to merging via communication. Any conflicts need to be resolved after inputting the data model (see above).