https://netsuiteprofessionals.com logo
Join Slack
Powered by
not sure if this is more of a <#CKMKB8QQP|> questi...
# sdf
a
not sure if this is more of a #CKMKB8QQP question but curious how others are handling this for SDF, especially if you have a team made up of both technical & functional users (where functional is someone who can do all non-development NS administration type tasks like reporting, custom fields, configuration, etc). i'm a developer and am comfortable using SDF, but we also wanted our functional NS consultants to start using it for transferring data between accounts/backing up workflows/etc, as bundles are being deprecated in favor of SDF for those purposes. we had just prepared a training on how to use eclipse for that for non-technical audiences, but now it's being deprecated, and i don't see any promised release date for VSCode's extension (plus i'm wary of building another training for VSCode if they're also going to deprecate that in another couple years...). webstorm costs money and it doesn't make sense to pay for a license for a functional consultant who will only use it for backing things up/moving from SB to production; and it's a non-starter to get them to use the command line haha. does anyone else have non-technical people using SDF and if so how have you approached it? or do you just put all backing up/transferring objects onto technical users now even though previously functional NS users could create/manage bundles?
👀 2
@Carlos Olivares (NS DevTools PM) curious from a NS roadmap perspective as well - do you intend for only technical people to use SDF (in lieu of bundles which anyone could use)? Or is VScode intended to be able to be used by functional-type users, and if so do you have a date that will be rolled out? Just concerned by the fact that both SuiteBundler and Eclipse are being deprecated, which only leaves the command line and webstorm available and therefore no options that make sense for non-technical users (since they can't learn command line/won't want to pay for an IDE).
s
@amy WebStorm IDE is great, and arguably easier to use than the original Eclipse IDE. I am also curious if you’ve used the Copy to Account functionality.. I often use that for moving objects from SB to PROD. When it works, it works great! I’ve never had a problem with pushing custom fields lists, searches, etc..
s
I agree with suitedev - I get the impression the 'copy to account' is the limited GUI version of SDF for non technical users. I still believe the real goal should be controlled deployment driven my automation - neither developers or functional folk directly.
m
When it works, Copy to Account is great, but it's a bit of a coin toss most of the time for me
😂 1
plusone 2
w
Never had a luck using copy to account. Always got a failed result. 😥
r
Indeed, most of the time it does not work the copy to account feature.
a
@amy The VSCODE extension is almost there, we are just waiting for some legal stuff to be finished, which will allow us to publish the extension for vscode. I would recommend you to try interactive CLI, it's user friendly and with a small learning curve as compared to the non-interactive cli aka (sdfcli). https://github.com/oracle/netsuite-suitecloud-sdk/tree/master/packages/node-cli#getting-started https://www.npmjs.com/package/@oracle/suitecloud-cli
👍 1
c
Thanks Ali, I would recommend in going that direction. SuiteCloud CLI for Node.js is very intuitive with the interactive mode
@amy, from the question in regards of roadmap and customer target. Eclipse will be not supported in 22.1, but still will be able to be use while the the authentication or api calls (REST/SOAP) from NetSuite accept them, we will not fix more issues or add new functionalities (which is not happening already), but it will not be decommission (last version will be 22.1) In regards of WebStorm, is the most user friendly plug-in we have because has a lot of UI elements that support the experience for non-technical users. On the other hand VsCode will be release soon (I can not share dates), but the experience will not be never like Eclipse or WebStorm because the approach is different and we are not replicating the experience from one product in another. VsCode is one of the most used Code Editors by the JS community, and has very well define standards and ways to interact with, and our extension will work as VsCode users expect things to work. On the other hand, the SuiteCloud CLI for Node.js, has a very well driven interactive experience that will guide the user to achieve their needs, therefore is not like other CLI´S where you have to know in advance the parameters to execute something, give it a try. If the trainings you want to prepare are incline to UI sweetness and click and point executions, then your option is definitely WebStorm. If you want a free easy to use tool, then the SuiteCloud CLI for Node.js is a great option. If you want to have it integrate it in a code editor, then VsCode will be there soon, but consider this will be the first version and as everything else, there will be gaps to be cover in upcoming releases. At any case, if your fear is that we will stop supporting one of those tools in the future, I will not tell that is not going to happen, but we are not planning to do it for now, our plans are to support the Development Tools ecosystem to improve how our customers build their solutions with a modern experience.
a
thanks all, this is super helpful food for thought and input! will check out the CLI for Node.js, and look forward to trying the VSCode extension once it's available. I agree that copy to account has been hit or miss for me (plus it's object by object so not as useful for a large migration between accounts) but hopefully that will continue to be improved upon as well.
2 Views
Open in Slack
PreviousNext
Powered by