Hello guys, we are trying to deploy an SDF SuiteApp to a Single Company Account, and we are getting an error around a Subsidiary Component (field) within the Project. Whilst I can appreciate this error isn't "incorrect", the SuiteBundler would handle this scenario and the Subsidiary Field would arrive. We are facing the same thing with other features like ESTIMATES, INVENTORY, LOCATIONS. Surely a variation of the SDF project doesn't need to be created for all permutation of account features/preferences? We have tried to cut the SuiteBundler out of the equation entirely, is SDF too primitive to be used without the SuiteBundler?

@Benjamin Carson you still need to use SuiteBundler to distribute a SuiteApp. I feel that the SuiteApp Market place is getting close to deprecating this need ... but probably not for another 6-12 months

@darrenhillconsulting Hi Darren, thanks for your message. I had thought as much. We had tried the SuiteBundler approach whereby we linked an SDF SuiteApp on page 1. What we found was Files/Folders are the only components not auto selected within the bundle, whilst this is fine for SuiteScript 1.x (with all libs included as dependencies via Script Record) this causes a massive headache with SuiteScript 2.x. We currently use SDF to create/deploy components to Development Accounts, we then SDF a locked/hidden SVN tag of the app to our Quality Assurance Accounts. Once QA passed, we then head over to Deployment, the issue here is that the Deployment Account may not have certain features enabled as required by the App, so we will have to revert to the SuiteBundler from DEV -> DEPLOY. I am attending SW 2020 this year, so will be really keen to see NetSuites plans for SuiteApp Market Place and SuiteApp Control Centre.