Hi Developers,
I have a question about best practice for developing in a team with SDF. While Netsuite has its own section about how to do this via SuiteBundler, it surprises me that not much information is available on SDF on how to develop in a team. SuiteAnswers also doesn't provide any further input.
I would like to ask you all about how to best develop in an environment with:
- multiple developers (let's say ~5)
- jointly working on the customization of one single production environment for their own company
- customizations include quick bug fixes, small scope improvements (let's say 1-2 days development) and larger scope features (1-2 weeks)
- managing source code via a versioning system (e.g. Git)
- a limited number of sandboxes (i.e., not every developer has an own sandbox)
- development done through SDF, not SuiteBundler
(I would assume that above reflects one realistic picture of a company using Netsuite and having own developers also taking care of customizations)
What kind of deployment process and selection of sandboxes should each developer choose to allow both quick deployments of bugfixes on the one hand, and work on longer customizations on the other? E.g.,
- Should in principle every developer get an own sandbox?
- Or should sandboxes be designated for specific purposes, e.g. one sandbox for testing quick fixes, another for longer development.
While each developer managing its own source code via an own branch is clearly one step, it does not resolve the issue of potentially conflicting edits in the same sandbox: While developer A might be working with a custom transaction requiring some 2 weeks of development time, another developer B might need to push a quick bug fix surrounding this custom transaction to production via SDF:
- Should the case be avoided that A and B work in the same sandbox?
- Or would B comment out the changes in the custom transaction XML that A has introduced, in case A and B work in the same sandbox?
Regarding the reason for choosing agains SuiteBundler
It is our understanding that Netsuite might fade out SuiteBundler sometime in the future and is not anymore developed. Furthermore, experience has shown us that with SuiteBundler, a lot of custom records / lists etc. referenced from custom transactions, workflows etc. , or forms, are not properly copied via SuiteBundler from sandbox to production, even after a sandbox refresh. This necessitates developers, after each new bundle install on production, to manually modify references records in production. Doing this possibly via a script might be an option, but the references needed manual fixing change after each sandbox refresh, so in total this results in a lot of time wasted and loopholes.
Thank you all for sharing your experience.