TFS version control in CRM without multiple orgs
I am looking for some data for version control in CRM. We are currently using Org unified development and maintaining CRM solution in TFS with Pacakger solution. We register the entire solution in TFS along with its checkout (checked out via Solution Packager). This way we can know what changes have occurred between any two decisions by comparing the extract files.
The problem with this approach is that we don't have low-level tracking that made specific settings / configurations . Understanding the limitations of CRM as a product, I think one possible solution to this problem would be to set up a parallel development process where individual developers will make changes to their respective Orgs and check in the changes (after the merge). Thanks to this approach, we can track the individual settings made by the developers, since they will record each change individually.
Is there any other approach whereby we can achieve this without having to create multiple Orgs for each developer?
source to share
The decision package must be one sequential package. When building from multiple sources, keeping all sequential will be a real challenge. At any point in the deployment cycle, you run the risk of providing a solution that cannot be imported.
Therefore, I strongly doubt that the proposed approach will be practical.
When you really need to track changes for individual team members, you might want to consider the following:
- Each developer has their own personal development environment, where they apply their settings.
- When ready, it only migrates the changed components to the overall organization crm.
- After that, he immediately checks his changes in TFS.
Of course, all team members need to sync the settings in the shared environment with their own. It requires the right toolbox to keep this practical and somewhat disciplined nature, but I think it's doable.
source to share