web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Best practices for rolling out solutions with bug fixes, new features?

(0) ShareShare
ReportReport
Posted on by 3,079

What are people's recommended practices around their own internal customized solution when rolling out bug fixes and new features?  Presumably there are times when you've got new feature development stretching over a period of time, but you'd like to roll out some bug fixes before that's done. 

  • How do you organize your solutions to keep everything organized and nothing getting into production before it's supposed to?  (But also not clobbering your own changes?) 
  • How many servers do you have other than production?  Do you use totally new servers, or just different organizations?
  • Do you do anything different step-wise for bug fixes vs features?
  • Do you make use of solution segmentation, if you're on a new enough version?  How?

Curious to hear what people have found works well (or doesn't).  Also, this is for a small environment (50 users, 2 customizers) - I assume scope may cause the answers to vary a bit.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    gdas Profile Picture
    50,091 Moderator on at

    Hi Allison,

    Here is my answers on top of your question. Hope this helps.

    How many servers do you have other than production?  

    =============================

    For my experience you should have at least 2 environment DEV, PROD(Always good if you have another instance UAT) for on premise.

    ==============================

    How do you organize your solutions to keep everything organized and nothing getting into production before it's supposed to?

    ==============================

    I believe you are aware about solution patching I would always recommend OOB feature instead of manually separate the solution component in terms of bug fixes or new features.

    [View:https://www.inogic.com/blog/2016/01/solution-patching-in-microsoft-dynamics-crm-2016/]

    ==============================

    What are people's recommended practices around their own internal customized solution when rolling out bug fixes and new features?

    ==============================

    Depends on your customization ,If  project size is small then I would recommend to maintain single unmanaged solution in DEV environment where you should keep your all customization. If your customer wants to change anything on top of your changes you can import unmanaged solution in PROD environment.

    For bug fixes I would suggest to use out of the box solution patching so that you can easily uninstall the patch for any kind of issues without impacting the base solution.

    And for new features or module if the entities and functionality are fully  different then  create new unmanaged solution and do your changes once done you can separately import into prod. Now if the entities are related to the base solution which you delivered in PROD  then  you can go for solution patching again.

    ==============================

    Do you use totally new servers, or just different organizations?

    ==============================

    I would always prefer having new servers to avoid down time.

    ==============================

    Do you do anything different step-wise for bug fixes vs features?

    ==============================

    I am not very much clear your question . It's depends on the fixes and features.

  • Suggested answer
    gdas Profile Picture
    50,091 Moderator on at

    In addition you can refer below post related to move the solution mmanaged or unmanaged.

    community.dynamics.com/.../270340

    community.dynamics.com/.../277270

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans