Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Solution and Release M...
Microsoft Dynamics CRM (Archived)

Solution and Release Management

(0) ShareShare
ReportReport
Posted on by AtulSharma 130

Scenario -

I have a team of 4 consultants. (i,e. Team members are C1, C2, C3, C4)

C1 is working on one functionality which involves Entity E1.

C2 is working on another functionality which involves Entity E1 and Entity E2.

C3 is implementing their functionality with Entity E1 and E3.

C4 is independently implementing the feature that involves Entity E4.

Now here is my Release Plan -

Release #1 will be for E1

Release #2 will be for E1, E2 and E4

Release #3 will be for E1, E2 and E3

Problem - 

Since I am managing all changes in single solution and all the customizations and changes are there only. So at the time of any release, other entities will be half cooked but I will have to export the solution as whole to import in the target environment. For example On Release #1, Only E1 is Expected to go in published but E2, E3 and E4 too will go together though they are complete. 

Questions -

  1. Do we have any mechanism so that we can stop not required to move into export?
  2. Is this the correct approach which we are following? 
  3. Any standard approach to work in this scenario?
  4. Any pointer to solution Management will be of great help?

I assume I have explained the scenario properly, Please let me know if you need any further clarification on this.

Thanks in advance

Atul Sharma

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Solution and Release Management

    Giving different perspective.. If you have time then explore the solution packager, it lets you pack/unpack the changes (components-based) you want into a solution and move on from there.

  • ashlega Profile Picture
    ashlega 34,477 on at
    RE: Solution and Release Management

    Hi Atul,

     there can be more than one answer to this. For example, you might want to set up your dev process in such a way that every consultant is working in their own dev and there is an integration enviornment. So, for example, for release 1 you might put E1 changes to the integration environment, and, then, to prod. But you would not put E2/3/4 changes to the integration environment at that time. Other consultants would have the same changes deployed into their dev environments.

    Another option might be to just ignore all this complexity and have everything deployed to prod all the time. If some of the entities are half-cooked at that time, simply limit access to them through the security roles.

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,494 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,309 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans