Two developers can work on the same model, however, they should coordinate their activities carefully, synchronize and refresh the model every now and again, and be aware of what each other is doing. Version control tools such as Git are currently not supported because changes are directly and continuously updated on the repository model.
Important note: Models can be exported to a file. However, this is for moving the model between environments e.g. dev to test or prod. You should never rely on the exported file for changes.
1 Comment
Cédric BLANC
said
about 2 years ago
Answer
Two developers can work on the same model, however, they should coordinate their activities carefully, synchronize and refresh the model every now and again, and be aware of what each other is doing. Version control tools such as Git are currently not supported because changes are directly and continuously updated on the repository model.
Important note: Models can be exported to a file. However, this is for moving the model between environments e.g. dev to test or prod. You should never rely on the exported file for changes.
Cédric BLANC
What are the best practices to merge changes done by several developers on the same model?
Reference - https://www.semarchy.com/doc/semarchy-xdm/xdm/5.3/Manage/models/overview.html
Two developers can work on the same model, however, they should coordinate their activities carefully, synchronize and refresh the model every now and again, and be aware of what each other is doing. Version control tools such as Git are currently not supported because changes are directly and continuously updated on the repository model.
Important note: Models can be exported to a file. However, this is for moving the model between environments e.g. dev to test or prod. You should never rely on the exported file for changes.
Cédric BLANC
Two developers can work on the same model, however, they should coordinate their activities carefully, synchronize and refresh the model every now and again, and be aware of what each other is doing. Version control tools such as Git are currently not supported because changes are directly and continuously updated on the repository model.
Important note: Models can be exported to a file. However, this is for moving the model between environments e.g. dev to test or prod. You should never rely on the exported file for changes.
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 274 topics