Hi Guys,
We have a team of omnistudio developers around 5 to 10 who are working on multiple usecases on our project. Currently we have one dev sandbox where our developers are working and have a source control tool with Copado for deployments. The work is already partitioned in a way that there is no overlap on the components and each developer is working on their own module with no conflicts. We have leadership asking on why we cannot have individual dev sandboxes for each developer compared to one sandbox which is quite the norm on standard apex salesforce development. I have been told that there is a lot of manual config work which needs to be done for deployments if we have more sandboxes increasing the deployment time. I would like to know the pros and cons of having an individual sandbox compared to one sandbox with work managed to avoid conflicts and considerations I need to be aware of to manage deployment and code conflicts better.
Buyan
I wouldn’t create individual sandboxes just because that is common for Apex. If OmniStudio work is already split cleanly and Copado is handling deployments, one shared dev sandbox can still work.
I’d add separate sandboxes only if conflicts or release collisions are actually slowing the team down. Otherwise, you may create more environment drift and deployment cleanup than you solve.
