project:adddependencies adds every custom transaction body and line field ------------------------------------ I have a test project with a single transaction form in it. When I use project:adddependencies, it adds literally every custom transaction field to the dependencies list, regardless of whether the field is shown on the form. I have multiple features under development in my sandbox, and would like to avoid deploying custom fields to production for the features that are not ready. What tactic might I be able to use?

Forms are difficult in this regard. The form has to know about a field to know whether the field is displayed on it or not, so you end up having a massive dependency list. You can move all custom objects that you don't want to deploy into a specific folder and then update your manifest to not include that folder. Or you can not include the form and recreate it manually.

Thanks, Jordan, good advice. I will try that first approach.

I’ve dealt with similar challenges and have a workaround that might help. We’ve developed a script that uses the change log to create tailored deploy.xml files, enabling us to deploy specific changes confidently without impacting other developments. While I need to update the project with some recent enhancements we’ve made internally, you can get the core idea and benefit from the existing setup. Check out the “Run npm run generate-manifests” section in the README of my GitHub project: NetSuite CustomModules Template. Feel free to fork, use, and contribute improvements via pull requests. Your insights and enhancements are welcome!

Thanks, Ryan, I will check it out!

I’ve updated the project with many of the adjustments I’ve made to this template over the last year. It’s much more robust now.