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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Customization best pra...
Customer experience | Sales, Customer Insights,...
Unanswered

Customization best practices for teams for developers

(0) ShareShare
ReportReport
Posted on by Benjamin Fallar III 245

Hi,

We are customizing Dynamics 365 CRM for a customer service and sales module, and we have a central development instance or sand box. One of our current challenges is when multiple developers are working on same entity, e.g. Incident form, they tend to overwrite each others work. We would like to avoid this issue in our development environment, since it is not ideal to have each developers to have their own instance of Dynamics CRM.

Is there any best practices on how to manage multiple (e.g. 3+) developers when doing customization on a sandbox development environment?

TIA,

Benj

I have the same question (0)
  • govardhan.reddy Profile Picture
    govardhan.reddy 10 on at
    RE: Customization best practices for teams for developers

    In Option2, if each developer  using some convention on what they are working, and not using others Forms,reports.etc will that help?

    I have similar problem, developrs work on different use cases they are adding their own fileds(each one adding 10+fileds) to same entity

    , i advised to look at extended entity and refer that from base entity..will that be a good idea?

  • govardhan.reddy Profile Picture
    govardhan.reddy 10 on at
    RE: Customization best practices for teams for developers

    whether each developer adding some additional fields to the entity?

  • David Jennaway Profile Picture
    David Jennaway 14,065 on at
    RE: Customization best practices for teams for developers

    You have 2 main options:

    1. Create a separate CRM organisation for each developer (these can be in the same environment), then another CRM organisation into which they deploy their changes and any conflicts are resolved (which will still need some manual decisions if e.g. 2 developers have modified the same form). You also need a means to deploy updates from the central CRM organisation down to each developer's organisation
    2. Developers work on the same CRM organisation and each have a separate solution that contains their changes, and they are disciplined about only including components that they change in their solution. Again, though, they could still overwrite each others' changes

    There are pros and cons of each. Option 1 gives more isolation, but also greater overhead for deploying changes

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft
Our Community Code of Conduct has been updated!

Quick Links

Responsible AI policies

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

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Rishabh Kanaskar Profile Picture

Rishabh Kanaskar 258

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 210

#3
Tom_Gioielli Profile Picture

Tom_Gioielli 77 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans