We have started using SDF recently. Our old pract...
# sdf
r
We have started using SDF recently. Our old practice when moving customization from SB to Production was using Bundles. This means the code usually resides in the SuiteBundles directory instead of the SuiteScript directory in Production. When creating a new Account Customization project, the SuiteBundles folder is not included. Is there a way to select the folder to upload to when uploading a file using the Webstorm plugin?
a
The way sdf works is that it creates mirror of the your local projects filecabinet in the netsuite filecabinet.. If for example you have a file in your local project under Filecabinet - > SuiteScripts -> folderA - > myscript.js. This will upload the file to netsuite filecabinet under same directories. If you dont have the same directories in Netsuite file cabinet, they are created automatically for you when you deploy or upload
r
Does this mean that if I add the SuiteBundles folder and the the Bundle folder, I can update the bundle files from the plugin?
n
No, that will not work, I think that because the SuiteBundles folder does not reside in the SuiteScripts folder it will fail. I suspect this is to prevent you messing about with the bundle and potentially having it fall out of line with the code base in the source account. You can however manually update the code directly in the account via the UI as long as the files are not locked. It was recently suggested to me, to make this less painful, use the drag and drop bundle to save opening the file manually. Unless someone can suggest a way to configure the plugin to get around this. 🙂 (I tried it only last week with my local folder structure a direct 1-2-1 of the filecabinet / bundle folders & path)
r
Thanks @NElliott. Manual it is
s
I always hated how NS bundler deploys to a different folder. I for one welcome SDF not forcing those different folder names between environments.