We’ve been using Account Customization packages for our code for a few years. We’re at the point where we are looking at trying to ‘convert’ our existing packages to Suite App(s) to be able to lock code down and not leak IP. We’ve spoken with support a few times, with varying success. We have a couple of issues: 1. It’s hard to get a ‘fresh’ netsuite environment to test deployments 2. We struggle with deploying custom segments to ANY environment and it generally involves hand-creating them through netsuite 3. We have years of existing js/custom fields/record types Has anyone done a conversion from AC packages to SuiteApps recently that we could consult with?

Using Github Actions on a self hosted runner for deployment and environment synchronization and since the update to Oauth 2.0, my action continues to fail with an error code 127. Maybe someone can see what I am still missing in my configuration. Only pieces changed is the installation of the suitecloud package and authentication variables. npm install -g --acceptSuiteCloudSDKLicense @oracle/suitecloud-cli 56 shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} 57 env: 58 JAVA_HOME: /opt/actions-runner/_work/_tool/Java_Oracle_jdk/17/x64 59 JAVA_HOME_17_X64: /opt/actions-runner/_work/_tool/Java_Oracle_jdk/17/x64 60 61 changed 58 packages in 10s 62 15 packages are looking for funding 63 run

npm fund

for details 65 echo * | base64 -d > /tmp/private-key.pem 66 shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} 67 env: 68 JAVA_HOME: /opt/actions-runner/_work/_tool/Java_Oracle_jdk/17/x64 69 JAVA_HOME_17_X64: /opt/actions-runner/_work/_tool/Java_Oracle_jdk/17/x64 71 ./node_modules/.bin/suitecloud accountsetupci --account ** --authid ***** --certificateid * --privatekeypath /tmp/private-key.pem 72 shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} 73 env: 74 JAVA_HOME: /opt/actions-runner/_work/_tool/Java_Oracle_jdk/17/x64 75 JAVA_HOME_17_X64: /opt/actions-runner/_work/_tool/Java_Oracle_jdk/17/x64 76 /opt/actions-runner/_work/_temp/34c20b99-4da0-46d9-9c63-094037dfbe4f.sh: line 1: ./node_modules/.bin/suitecloud: No such file or directory 77 Error: Process completed with exit code 127.

Validation return this error message Expected BEGIN_OBJECT but was STRING at line 2 column 1 path $

New issue in WebStorm recently - a new project is not creating a project.json file in the directory. Easy enough to copy over one from a different project, but this is preventing me from importing objects (but strangely not files) from our NS instance. Anyone else seeing this? Or am I missing something?

Did you configure/select the project?

Details: All term references must be to terms in translationcollection objects in the same SuiteCloud project. Terms cannot be referenced in other SuiteCloud projects, bundles, or SuiteApps.

In the past I have overcome this by including the translationcollection in the project, however I have references to some locked translation strings and cannot import the collection into my project. Having it listed as manifest fails with the above. Anyone find a workaround for such cases?

Has anyone tried and failed where this update from NetSuite is concerned? NetSuite: Changes to Script Deployment Record Audience Fields

Hi all ... I'm getting a

The "XXXXXXXXX" authentication ID is not available. Check your authentication credentials and try again.

in one project .. but all the other projects deploy just fine.

I upgraded to sdfcli (java) 2025.1 and now I get a warning "Setting the <allroles> field to 'T' only selects all internal roles." for every single script in my project. Is there any way to confirm I just want internal roles so it can stop warning me?

Any suggestions on

project:deploy --dryrun

in a CI/CD environment without secure storage? I tried with environment variable

SUITECLOUD_CI

, which changed the error from

Secure storage is inaccessible. Ensure that the secure storage in your system is properly configured and accessible.

to

The following environment variables are currently set: SUITECLOUD_CI.
The operation you are trying to perform is not allowed with the current environment variable configuration.

The normal deploy after seems to work. I'm using the

dryrun

to try and catch issues before it actually goes and touches the environment.

Hey! I'm using the webstorm suitecloud plugin on Ubuntu. Authentication was working fine until some days ago. I get the error message:

The passkey required to decrypt your credentials is missing.
Try deleting the credentials file ~/.suitecloud-sdk/credentials_browser_based.p12 and setting up your account again.

I already purged the .suitecloud-sdk folder and also purged the project. Authentication is empty. When I create a new token (browser-based) I get the same message again. Any ideas what could be causing this?

Im pushing a SuiteApp we built and it deploys no problem to one account but when I push to a second account I am getting this error and the file it is referring to is a SuiteLet: Details: SuiteScript 2.1 entry point scripts must implement one script type function.

Hello, We are moving from one NS instance to another. Everything has been going smoothly so far. we have run into an issue when trying to move a entry form We are getting this error: To install this SuiteCloud project, the SUBSCRIPTIONBILLING(Subscription Billing) feature must be enabled in the account. However this feature is not present on the source or destination account, it cannot even be enabled. I’ve tried deleting it from the manifest or setting it to false but it still throws the error when trying to deploy

Any suggestions on moving custom transaction forms from one sandbox to another sandbox? We are getting a ton of An unexpected error has occurred as well as "field position must be set to BOTTOM". Both are on 2025.1 under the same instance and it just doesn't seem manageable to have to comment out all this from the XML file. We're using Webstorm and the latest netuiste plugin. Nestuite support wasn't very helpful and we are considering using bundles again.

I’m getting a “Internal error encountered (Null pointer exception).` when i try to run

node ./node_modules/@oracle/suitecloud-cli/src/suitecloud.js project:adddependencies

. I’ve debugged down to it seems to possibly be something to do with the jar execution. Anyone seen this issue before or know what it might be?

Hi all, I'm trying to run some custom logic on upload and deploy using

suitecloud.config.js

and while it works for the CLI it seems to be ignored by the Webstorm plugin, is this not supported? I was also surprised to find that the Webstorm plugin does not use the same authid store as the CLI but it seems this discussion has been had already and I need to set some environment variables

I'm using the sdf cli and recently installed the latest version. I've noticed on the recent version that the cli keeps processing for a really long time like an hour. when I check the audit trail though it shows deployment complete

it also shows deployment completed in under 10 minutes

For WebStorm users: Do we know if the latest NS SDK works with the new 2025.1 from JetBrains? Inquiring minds want to know (before trying it themselves because they're in the middle of a large project)!

What is the best library or plugin for Netsuite suitescript 2.1/2.0 IntelliSense you use in vscode ?

This message was deleted.

In a Condition on a Workflow in SDF, the Validation is complaining when I replaced an {ACCOUNT_SPECIFIC_VALUE] with the internal ID of a custom form, which made sense to me since this condition was about the STDBODYCUSTOMFORM field:

<parameter>
 <name>Transaction Form1</name>
 <selectrecordtype>-171</selectrecordtype>
 <value>184</value>
</parameter>

--

Details: The Transaction Form1 condition builder parameter in the workflowaction2365 setfieldvalueaction contains a value, 184, that is not valid for the -171 selectrecordtype.

What kind of value is it expecting instead?

In VSCode... is there a way to set a default setting for this, for deploying?

Anyone using WebStorm 2025.1.1 with the SDF Plugin that can confirm is working correctly?

does anyone know if there’s already a defect or enhancement for supporting preferences on Roles? the help page for SDF Roles calls out the subsidiary field, forms sublist, searches sublist, and dashboard sublist as not supported in the Roles XML; but although I have preferences set in the sublist on my custom role, they don’t show up when importing the object.

hello! anybody has encountered this error in SDF? I am only moving mostly custom records. acouple of custom list, body fields, custom tabs, search and 1 custom transaction

An error occured during validation of Custom Objects against the account
Details: A script is attempting to edit the statuses sublist. This sublist is currently in read-only mode and cannot be edited. Contact your NetSuite administrator to disable the script if you need to submit this record.

X-posting from #C29HQS63G, I an into an issue and there's a confirmed bug by netsuite support that after a SB refresh from PROD, the installed versions of suiteapps to are confused and it thinks the latest version is installed when its not (in either account). You can't do an SDF upgrade of the app from webstorm/cli due to the versioning either. You really have 2 options. Let support fix it with an unknown timeline or update the app version (no other changes) and re-package the app so that the versions are no longer aligned so you can update in the SB.

@Diego Lemos, another great channel here

WebStorm 2025.1.3 and Plugin 2025.1.0 Getting the message

Machine-to-machine authentication is not allowed for the current execution context.
For more information, see <https://system.netsuite.com/app/help/helpcenter.nl?fid=article_0113125121.html>

Anyone know how I can solve this?

Anyone got an automated pipeline for building and deploying objects? Primarily I'm looking for building and deploying suitescripts from VS Code but any examples of any object type would be good