https://netsuiteprofessionals.com logo
Join Slack
Powered by
:wave: Hi everyone, I’d love to hear from people u...
# sdf
v
👋 Hi everyone, I’d love to hear from people using SDF (SuiteCloud Development Framework): what’s your biggest pain point with it today? It could be anything from setup and project structure to deployment, testing, debugging, or day-to-day development. A quick reply is perfect — what are you trying to do, and where does SDF make it harder than it should be? Thanks in advance for sharing your experience! 🙌
c
My biggest pain point when getting started was properly structuring a project with TypeScript support. At the time there wasn't a lot of proper documentation for handling it, and it was a journey to get started. A nice structured starter project/template would make new projects easier to bootstrap. For day to day development proper es module support is hopefully on the horizon since typescript 6/7 has dropped AMD module support. Proper SS 2.1 debugging support in Firefox would be amazing. I have been unable to get it working, and have to keep Chrome installed just to debug some things.
k
I liked the idea of having the config:import, there is also a way to deploy it ? (I didn't check)
e
Two things as far a pain points; 
ACCOUNT_SPECIFIC_VALUE
in objects, and not being able to specify a specific deploy.xml file to use.
💯 2
d
Thanks for asking, @Verónica! I have two asks, both about the SuiteCloud CLI and CI/CD:
1. Let us point to a specific 
deploy.xml
and 
project.json
(auth ID) when we run a command, rather than having them read from fixed locations in the project. For example:
suitecloud project:deploy --deploy-file deploy.qa.xml --project-config ci/project.qa.json
CI/CD: a single GitLab pipeline could deploy to different accounts, or deploy different sets of objects, by passing flags. Today we have to generate or swap files before each run. This is also a +1 to @ehcanadian.
Fewer accidental deploys to the wrong account: at the moment the target account is whatever 
project.json
last pointed to. If developers had to name the account on the command line, deploying from a dev environment would be a deliberate choice, and nobody would push to the wrong account because of a stale default.
2. SACC commands in the CLI. We'd like a much larger set of SuiteApp Control Center actions available from the command line, backed by the SACC REST API: upload a packaged version, release it to the Leading/Lagging phase, push-upgrade the install base, and deprecate. Our pipeline already builds, packages and tags each release. With these commands, it could take a SuiteApp all the way from merge to a released version in SACC.
(Checked against CLI 4.1.0: 
project:deploy
has no 
--authid
or config-file option today. The target account is always whatever 
project.json
says, and none of the commands touch SACC.)
➕ 3
m
I'd like to have a "Compare file/object with Account..." with a dialog allowing me to select an account to compare against. If I want to compare a script with production today, I have to change the project default account to production, then perform the compare. This can lead to an accidental push to production later if the dev forgets to change their project default back to a sandbox account.
c
A link to account management in Webstorm in addition to the NetSuite Settings link. Just saves a few clicks and I find myself having to navigate to it when doing app development where we have multiple accounts to deploy a build to. Deploy to account... seems to open the current account for auth rather than letting me select an account to deploy to. If it just let me select an account, that would be good too unless I just have it configured incorrectly?
m
Also, show me which account is currently configured for the project in WebStorm/VSCode. Show it in the status bar or the toolbar so I can see at a glance which account is currently selected.
💯 2
c
Hopefully not too nit picky. Just seems like a nice QOL update. Or i'm getting old and next thing you know i'm gonna be licking my thumbs to turn pages.
s
it’d be great if datasets/workbooks/translationcollections weren’t such a frankenstein monster
c
Mike, In vs code if you're in a project file it you should see the account in the bottom left. Assuming you have the Netsuite extension.
m
Thanks. I said VSCode, but I work mostly in WebStorm. I probably shouldn't have included that without checking. 🙂
3 Views
Open in Slack
PreviousNext
Powered by