Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM online Solutions, ...
Microsoft Dynamics CRM (Archived)

CRM online Solutions, UAT and best practise

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

I have recently started taking on the lead role for a Dynamics CRM in our organisation and I wanted to know what the best practices were for managing solutions/patches and moving UAT stuff to production. Keeping it short

We have two UAT systems available - I want to be able to move stuff from UAT to live - but sometimes UAT takes longer than certain changes that need to happen to live. So how do you manage changes to a live system - whilst working on stuff in a UAT system - without ending up with a bunch of merge conflicts at the end?

At the moment it seems like i have to have one solution in UAT with everything in it just so that if someone wants one specific displayname/view to be changed I change it in UAT and then move that to live.... which seems a lot more work than just customizing the default solution - but this is frowned upon?

Any links/guidance? I want be able to work on long and short projects in UAT whilst also being flexible enough to make changes in the live system if there is an issue that needs to be fixed.

*This post is locked for comments

  • Suggested answer
    Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: CRM online Solutions, UAT and best practise

    Hi David,

    Not sure kind of process your organization is using Agile, Waterfall, SCRUM, but the point is you have to decide what comes out in every release.

    It is very possible that your releases should be a little smaller, so that UAT will only be testing a subset of components everytime, and not a large solution. This will allow you to have deployments quicker and release the features to production.

    You can use different numbering sequences for your releases, such that if you are doing a major release your are splitting your actual implementation into a few minor releases.

    Example:

    Your solution 1.4 has 20 features/components in it.

    Split your solution 1.4 into 1.4.1 - 1.4.4.

    Each of the solutions will have 5 features, released in order of precedence or importance.

    While UAT is working on 1.4.1, your development team will already be on the next minor release.

    That way every minor release that UAT completed can be deployed to production, and the next one will be ready for them.

    This eliminated a little bit in the deployment process.

    If you are not using any particular process, take a look at Neil Benson's SCRUM for Dynamics 365. It might be a good starting point for the organization. http://scrum365.customery.com

    Hope this helps.

  • Suggested answer
    TheMarkChristie Profile Picture
    TheMarkChristie 10,328 on at
    RE: CRM online Solutions, UAT and best practise

    Hi David,

    Here in my blog I talk about Solutions, Numbering and Best practise

    community.dynamics.com/.../dynamics-365-version-numbers-amp-solution-manag

    It also depends on the size of your organisation as some like DEV>UAT>Staging>Live and others if there is training will go DEV>UAT>Staging>Training>Live

Under review

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.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans