Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We are 4 developer supposed to work on a same CRM instance for our next CRM project.
We are planning to use Solution Packager to decompose solution file into folder structure containing XML files representing each component of the CRM solution.
We are using Git for version controlling.
Currently we foresee some issues due to which we suspect it will add more overheads or involve manual intervention to avoid some of the conflicts.
On the Microsoft website, it gives an example where the CRM solution file is stored under Source Control but developer A and developer B have both independently made changes to components of that solution. It says:
Developer B is ready next following developer A.
To me it seems this will require a lot of manual intervention for the changes to merge.. which seems not too ideal.
Wondering if anyone can share some ideas on what should be the best practice for multiple developers to work on Single CRM instance where each developer is supposed to customize components and plug-ins? We are planning to use Git as ALM, and Solution Packager to decompose a solution so that we can track XML files in the Git.
Any help on this will be much appreciated.
I would recommend to have a git hook that exports the solution from a given organization and extracts it with the solution packager. All devs need to have that git hook in there repo since git hooks are not in the versioning themselves.
Also I would advise you to make temporary git branches for the stuff you are working on to not interfere with other developers and their work. The catch is, probably you need a copy of the organization for every branch to make it work well.
Also, if you use the solution packager, you may want to use also it's mapping capability to map local webresources into the solution so if you pack the solution again you always have the latest webresources or even plugins.
We are exactly facing the same issue and have made so many scenarios.
I don't have any answer yet but I found something that make me anxious. Let say, a developer import a solution in one organisation( not the one use to create it). If he re-export it without any Change. You extract it, you realise that all entities and savequeries are flagged as change.
When you compare those to the original, you realise that the objectypecode for entities and returntypecode for savequeries both change
The only explanation I guest is that crm doesn't preserve object code between org and since savequeries reference entities they get change too to remain consistent.
This is a huge issue since assumptions for version control is that only change made by developper should check in.
I have an appointment with someone from Microsoft to check with him.
Let keep in touch so we could share idea.
We are having similar problem. Henri - Did you receive any input from Microsoft on this? Could you please share with community?
Has any best practice emerged for how to manage the software development life-cycle for solutions with git?
We have copied all sandboxes from production environment to have all objectypecode and other IDs the same. Also, with each opportunity we do a copy of all environments up to dev.
Hope this helps.
Business Applications communities