Hi all. Looking to see what folks do to move confi...
# general
b
Hi all. Looking to see what folks do to move configuration, saved searches, workflows, etc from sandbox to production. We have been been recreating everything manually and would like to incorporate some automation at least. We have not yet explored creating bundles or "Copy to Account." What are your experiences of what works, what doesn't work, things to watch out for? Are there other options available besides bundles and copy to account? Thanks! I searched the channel and found mentions of bundles being deprecated and Copy to Account not working well (at least for workflows). 🤷‍♀️
e
Copy to Account doesn’t seem to work consistently well for any object. We use SDF and migrate most things by command line. We’ve had to write some additional scripts to help automate some of that. None of it is great. There’s a lot of room for NetSuite to improve on this IMO.
e
Copy to Account doesnt work. Bundles are more consistent. No experience with SDF.
t
I have had issues with both the Copy to Account and doing it as a bundle. I have heard about using SDF, but have not had time to look into it.
e
Copy to Account uses the same approach as SDF except that if it encounters dependency issues it just dies. SDF can deploy objects (script records, script deployments, custom records, custom lists) and files (scripts and other files). For custom records, SDF can copy over the records themselves if you let SDF generate the XML representation of those records. SDF doesn't do well with workflows.
e
I really like NS customization options, it just clicks for me. But deployment is very lacking.
b
Thanks for the responses! Definitely seems Netsuite has much room for improvement. Question about using SDF to deploy to production. From a quick review of the NS documentation, I gather this is something that would be handled by DevOps with support from Sys Admins? At least in an organization like ours where Sys Admins handle configuration and are not developers.
e
You'll need DevOps to create the SDF project and then download the files and objects that you need to push to production and then upload it to your source control repository. SysAdmins can then clone the repo and simply need to change the authentication id for the production environment before deploying it. That will give you separation of duties control so that those who develop code aren't the ones deploying to production. But technically anyone who knows their way around SDF can perform both download and upload operations into any environment that they can authenticate in.
b
thank you!
f
I'd recommend SDF with CI/CD. Build your automated testing into the process, and then deploy several smaller repos instead of one big one. Something important to always think about is how do you roll back. This process takes a bit of time up front, but I think you will find it faster.