How do you handle deploy.xml and source control

AI generated answer (using internal Slack threads):

Handling

deploy.xml

and source control in NetSuite can be achieved through SuiteCloud Development Framework (SDF). Here are some strategies discussed in the threads: 1. Separate XML Files for Specific Updates: For large repositories containing hundreds of files, you can create separate

deploy.xml

and

manifest.xml

for specific files of a particular change request. Save them in a folder named after the Change Request and use them for the deployment of the specific piece of code when required. 2. Import Old Script Record XML: If you have a new script and deployment defined that is going to replace two existing scripts that are not part of any SDF project, you can import the old script record XML. You can either update the existing script record with the new SuiteScript file path directory or set their status through the XML. Here are the code snippets for both:

<scriptfile>[/SuiteScripts/{NewFile}.js]</scriptfile>

OR

<status>NOT SCHEDULED</status>

3. External Dependencies: You can make the existing scriptIds external dependencies and include the script deployment objects to change them to undeployed. This way, the scripts themselves remain intact, but they are undeployed so they no longer run when the new script runs. Remember, these strategies require a good understanding of SDF and SuiteCloud Node CLI. You might need to specify the existing script files and scriptId objects within the original scripts, but you do not have to include them in your SDF project. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******