function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

Changing the developing architecture

Hi everyone,

Imagine the next situation: a company starts developing an application in Salesforce, using a Developer Org and creating managed packages. The project grows and the company started to have multiple clients, the developers solved the integration problems using different extension packages. Until here everything is OK, the problem shows up when the developer team is also growing and appears the necessity of handle different developments at the same time. Salesforce recommends having one dev org per developer, but copying all the metadata to developers orgs is really difficult (multi-currency feature enabled, removing the prefix, un-deprecating fields and so on). An alternative is to use sandboxes created from production. But this approach is also problematic, because the package is already installed in sandbox, and it's not possible to modify its code.


We are kind of lost right now.


Does anyone know how we could face this problem?
How can we organize our development process into the salesforce infrastructure with:
6 developers

One application in development already in a Managed Packaged (in the way that all those 6 devs can work without interfering each other's work)
One application that has special features activated as multi-currency, partner portal, that takes time to activate
How can we split our developer org in different ones (dev or sandboxes) to work efficiently?


Thanks in advance.


No ideas, then?