Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Version Control and Reference data
To ensure that changes in reference data are shared between users in a version-controlled project that is deployed as multiple private models, you should periodically export the reference data from the model where the changes were made, and import it into the other models maintained by the team.
Guide:
Topic |
Detail |
See also |
---|---|---|
Reference Data |
Reference data is data that is used across a model or project; it is not package-specific.
|
|
Version Control in Enterprise Architect |
Version control in Enterprise Architect operates at package level, and therefore does not capture changes in reference data. Where version control is used in a multiple private model set up, changes in reference data are not brought into the model when packages are updated from version control.
|
|
Sharing Reference Data |
In a Shared Model environment, all users are accessing the same Project Reference data. However, in a Multiple Private Model environment, to ensure that changes in reference data are shared between users in a version-controlled project, you should periodically export the reference data from the model where the changes were made, and import it into the other models maintained by the team.
|
|
Version control of Reference Data |
Reference data is exported and imported as an XMI file, which contains whatever types of reference data you want to transfer. To place your project reference data under version control, you should export the data as an XMI file and apply version control to the file using your version control software, external to Enterprise Architect.
|