It is a best practice to have only one model edition open and editable when creating an MDM model for deployment.
- Full information on Model Management in Convergence for MDM can be found here:
http://www.semarchy.com/doc/SEMDG/html/Models-Management.html
- Full information on Deployment in Convergence for MDM can be found here:
http://www.semarchy.com/doc/SEMDG/html/Deployment.html
A few customers have come across problems when they do not follow this best practice and have been making changes to their model but do not see these changes in the deployed Application UI.
The reason this has happened is because they have created multiple versions of their model, without going through the process of closing a model edition, ready for deployment. A model edition is deployed to a Data Location which then makes the Application UI available for that edition. Therefore you must ensure that the model edition you are updating is the one that is deployed to the Data Location.
Here is an example where there are 2 open model editions:
However, notice in the Data Location, the deployed model is CustomerAndFinancialMDM [0.0] not CustomerAndFinancialMDM2 [0.0]:
Therefore any changes made to CustomerAndFinancialMDM2 [0.0] will not be seen in the Application UI. For the changes to be seen, this model edition must be installed and deployed in the Data Location (see links above for instructions for doing this).
(Please also note, if you discover you have a model edition with a number appended to the end and you or another user has not explicitly created this new version (e.g. CustomerAndFinancialMDM2 [0.0]), this will happen if you have exported the open model edition for CustomerAndFinancialMDM [0.0] and then imported it to the same environment where you already have an open CustomerAndFinancialMDM [0.0] model edition. This will only happen in a Design time repository as a Deployment repository will only let you import a closed model edition)
The best practice, as described in the links above is to start with one model edition and develop and make changes in that one edition (usually v0.0). Once the model is ready to be deployed to test or production, the model should be closed. This action automatically closes the model edition so it can be deployed but also opens a new edition of the same model which can then be further developed for the next release to production.