Greetings everyone. Wondering if anyone of you has...
# administration
f
Greetings everyone. Wondering if anyone of you has worked with a Development Sandbox environment (aka a Sandbox without the Data from production) to reduce costs. And if you have, how did this affect your developers work.
k
It can be useful if you have multiple ongoing projects at a time
That said - you can't get a development sandbox without a real sandbox
At least, last I knew
f
Yeah, we have 2 sandbox environments right now, Oracle has suggested having a Development sandbox so maybe we can forgo one of them to reduce costs.
k
Now, that can be beneficial - write the code in your development account - figure out if it works, deploy to sandbox, for further testing if desired, and then deploy to production.
However, the multiple sandboxes can be nice because you can have different streams of development ongoing without tripping over one another, but most companies doing that kind of thing don't mind shelling out a bit more for a 2nd sandbox
After all, they are paying quite a bit in developer salary/time to accomplish that to begin with
f
Sounds correct. Have you experienced any cons about using this, that might have affected the developers work. Or anything like that.
k
Well, the biggest thing is you can't just push production/sandbox data to the development accounts
which means you have to spend more effort maintaining it and keeping it up to date enough to have valid tests
unless you only use the development account to write a specific subset of code - and then retest it in sandbox
either way - it adds more administrative headache in comparison to the easier method of performing a refresh
f
Sounds about right of what I was thinking, if our production environment is already also filled with a lot of customizations, the work to push that info into the development environment can be a dreadful work.
In case the new projects need to interact with former ones
k
Right. SDF (which you should be using anyways if you are doing significant development) can facilitate that process
I would advise against trying to use bundles to deploy to your development account
f
Yeah we are already pushing our development team away from bundles.
Just got to deal with the few that are reluctant to change methods.
s
@Fernando Aceves I just saw this question, development account isn't meant to be used like this. If you aren't on one world and you only have one subsidiary, it can be considered, otherwise, the dev account limits the number of subsidiaries you can have. So you'd have to throw intercompany dev, multibook dev, etc out the window. Not to mention Sandbox bundling into Production will not deploy as a bundle. (The way that I think is more optimal) If you go to Dev, create a bundle and deploy to sandbox it will deploy it as a bundle. It'll be under the suitebundles\XXXXX directory, instead of being in Suitescripts\. The way it should be and preferred. This is because sandbox, is an environment type of it's own, Development account is considered to be a production account, and the two types will differ in deployment behavior of bundles. Last thing you want is the same script in multiple bundles to be maintained in multiple locations of your account. At least, that's not something I'd want work with Big big caution there. big big caution
f
Thanks for the response!