With project version management, you can manage changes on your Connectivity Studio projects and all related components. This includes all project details and components, like messages, web service actions, documents, connectors, type conversion, or transformations. Changes to project details and related components are stored by project version. Each project version is stored as a file in the file storage folder as defined in the Connectivity studio parameters.
You can use project version management to synchronize projects between several D365 F&SCM environments. For version management, to work properly, the file storage folder, as defined in the Connectivity studio parameters, must be the same for all environments between which project versions must be synchronized. So, the version files are stored centrally and can be accessed by all applicable environments.
In Connectivity Studio, if version management is active, you:
Manage versions on project level only, including all project components and settings.
Must check out a project to make changes to the project or its components.
Must check in a project to make changes generally available for other environments.
Can restore a project version or get the latest project version.
This picture shows an example of a typical environment setup. For each environment, project version management is active, using the same Azure Storage Account and folder to store project version files. In this case, the project is checked out on the Development environment, changes are made, and the project is checked in. Because the changes are required in the Acceptance environment, Get latest is done here.
.png)
You can use project version management, for example, for these scenarios:
Project changes: A change to a project component in an environment can be easily applied to other environments.
Issue resolution: During testing, you can find and solve an issue in a project component in one environment. The solution to the issue can be easily applied to other environments.
Updates in the test environment: In a test environment, project components are often changed. Using project versions, you make sure that changes are saved, and you can always restore a previous project version.