Our company has just made me in charge of a large CRM implementation that was developed by a third party and has now been dumped on our department. We have our Dynamics implementations so I am familiar with D365 however I have never had to deal with such a convoluted and messy system. This CRM/Dataverse implementation doesn't have any clearly defined deployment strategy. There are like 3 to 4 dozen managed solutions in production instance with their names after Jira tickets!! Whereas we inhouse either always had a "Core" solution style or Solutions defined around shared components. My first job is to clean up this new implementation. On the outside, it looks like creating new solutions and just adding old components into these from the old solutions in the correct order and making sure every component is there in the new solutions, deploy that on test and check everything work. If it does, remove the old two dozen solutions named after tickets. Test again with an eye on any data loss because if a column wasn't there in the new solutions but was there in old messy solutions, it will get deleted and all data will be lost. But I am also worried about circular dependencies, conn references and environment variables. Frankly, this is the first time I am doing this kind of "clean up" on this huge scale. If anyone has done this in the past, I would appreciate any advice you can give, things to keep an eye and edge cases to be aware of.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Share
Report
All responses (
Answers (
25
