⭐ Hello NetSuite Professionals!, SuiteCloud SDK Development Tools 21.2 is finally here! ⭐ See bellow the list of additions included in all our tools. For more details please visit our Official Release Notes. We are thrilled about SuiteCloud Extension for Visual Studio Code release. After waiting for so long, we finally bring to all of you the very first version of this extension, which will allow you to build your SuiteCloud customization independently to any other SuiteCloud tool. This new Open Source Oracle NetSuite (UPL) product is delivered for all our SuiteCloud developer's community that was looking to interact with SDF leveraging with this amazing free (no license needed) lightweight code editor. Committed to building a developer's SDK that works as you expect, we add to the set of products this extension that combined with the SuiteCloud CLI for Node.js and Unit Testing Framework Integration with Jest (+ Custom SuiteScript Stubs), enables you to build an extraordinary solution for your development environments. Note: SuiteCloud IDE Plug-in for WebStorm and SuiteCloud CLI for Java  are also AMAZING 🤓            (This will be the very last release for SuiteCloud IDE plugin for Eclipse, so we strongly advise you to transition to the SuiteCloud Extension for Visual Studio Code or the SuiteCloud IDE Plug-In for WebStorm) With this release you will be able to: • Authenticate using TBA (Web Authentication or Save Token) • Switch Accounts (AuthId) • Deploy • Add Dependencies to the Manifest • Validate (Server Validation) • Upload File • Update  Object From Account • Import Objects and Files • List Objects and Files • Create SuiteCloud Projects (and include Unit testing with Jest) • Create SuiteScript Files (and inject SuiteScript Modules) We have still room to improve (we are on it), but with this kit of functionalities you will be set to code your SuiteCloud customization. On top of the new release, we are also including for all our SDK (WebStorm, VSCode,  Eclipse, CLI for Node and CLI for Java): • Support for Installation Preferences  (new feature)  by adding the capability to define what to do with Custom Values and Custom Instances when a SuiteApp is updated or deployed (this does not apply for Account Customization Projects). • SDF Objects Support For SuiteCloud CLI for Node.js  and  SuiteCloud CLI for Java ,  you can now create SuiteScript Files injecting SuiteScript Modules. SuiteCloud IDE Plug-in for Eclipse  ⚠️* _We advise and recommend to transition to WebStorm if you haven´t done it yet. SuiteCloud IDE Plug-in for Eclipse will not be supported starting on 22.1 release, and on top of that, there will not be any enhancement related specifically to this IDE until then._* Here are the links to download the 21.2 Major Release: The URL to download the latest tools version is available, so if you want to stay to the previous one you should specify it (for more info, check the Help Center). • SuiteCloud IDE 2021.2 Plug-in for VsCode • SuiteCloud IDE 2021.2 Plug-in for WebStorm • SuiteCloud 2021.2 CLI for Node • SuiteCloud 2021.2 CLI for Java Please, share with me your opinions and experiences after you give them a try! Thank you@

When you say “Upload File” do you mean we can download & upload individual files easily like how you would with something like Git?

Upload file to the file cabinet folders, this is specifically for the one that you have open in your editor view

cool

No in this version

dang

that feature could be reproduced by using Git (with some kind of Gitflow) and making your master branch the production account, and then running a diff between feature branch and master branch (ir development) could show the differences (just a comment, not an official advise of any sort)

I use different git branches for the sandboxes. Works well

how do you get stuff from git to the File Cabinet?

you can built a CI/CD Pipeline with any of the CLI's

I actually do things a little differently... I have a git repo with everything in, then for each project I'm working on I have an account customisation project. The account customisation project has only the changed files in the deploy.xml - the files themselves are symbolic linked from the checked out git repo into the account customisation project. I did this so that I'm only ever working with current in-dev files for a specific purpose at any one time (so no risk of bad uploads breaking things etc), and also so that I don't have to mess around with git too much as it's all there in 1 folder. Might be over-complicated for some, but it works for me

hmmm. This all sounds like it might be beyond me.

@Carlos Olivares (NS DevTools PM) +1 for the compare diff to file cabinet for me as well, we use that feature a lot currently - looking forward to https://github.com/oracle/netsuite-suitecloud-sdk/tree/feature/vs-code/file-diff getting merged in ;)

Thanls for the feedback!

@CD That's what we do too. But... I want my devs to stop making changes directly in netsuite w/out updating the git repo. What I want to do next is have have the branch pushed to the netsuite environment, if it overwrites your changes in netsuite because you didn't update the code in github, then hopefully you remember next time 😄

@Carlos Olivares (NS DevTools PM) looks like there is no SDF SuiteCloud Project

Validate

command mapped either? would like that one as well

@Carlos Olivares (NS DevTools PM) the link for vscode 404s

When Clicking on the link for the VS code plugin 👇🏿