Before I go about setting up the CLI, is it possible to use the the IDE plugin and CLI with the same project? The deploy dialog is modal so it prevents focus on another project in WebStorm, which prevents me from working on something else for the 10-12 minutes it takes to validate/deploy. I figure if I could use the CLI I'd get some time back. Looking at the docs the structure is different so I figured it's worth asking, just in case.

I think the latest version is supposed to have unified configuration between the CLI and plugin? I haven't tested that yet.

This is probably a shot in the dark, but has anyone seen this before and know how to resolve it?

The subtab id value, entityaccess, is either invalid or does not exist in the account. The value must be a valid system value or a custom value.

Update: I moved the xml file for the object to another folder and it deployed successfully. I can't explain it, but I'll take it. 🤷‍♂️

Doesn't look like I'm able to import Bundle Components w/ the WebStorm Plugin. Can anyone confirm? Can't find anything in the docs.

Question about node cli, specifically

suitecloud project:validate

. I'm getting an exit code of 0 when validation fails. I would think you would get some other exit code, is this expected?

Hello, anyone encoutering this error on Eclipse? I'm using the plugin for 2020.2 since the NS account is upgraded to 2020.2

I guess I could sneak this in here as it's somewhat related. I am trying to convert one specific bundle into an SDF project using the Convert to SDF project button. I've tried a couple which were converted fine, but I have one bundle which is not showing up in the SDF_conversions folder in the file cabinet, even though the button is not greyed out which I understood to indicate that the conversion is complete. Any ideas why it might not show up? Would it just fail silently if the bundle contains things which cannot be converted?

I've recently updated my eclipse suitecloud IDE plug-in to use the 2020.1 Update Site. For some reason the actual web services that are being used to hit the account are showing that they are still using 2017.1 (ex. "core_2017_1.platform.webservices.netsuite.com") is this normal? If not how do I fix this?

Question about Publisher ID and SuiteApps. Do I need to buy into the SDN to build a simple SuiteApp and test deploy?

Hi All, I have a question about entity field object. I have this custom entity field applies to Customer and Vendor. I set the sourcing list to Parent field and Source from to the field itself. It’s working setting on UI, however, when I download XML object and tried to deploy to account, I got validation error “An error occurred during custom object validation. (custentity_gw_gui_address) Details: The [scriptid=custentity_gw_gui_address] object referenced by the sourcefrom field in the null subrecord must not reference itself” Does anyone know how do I set xml so the object can be deployed successfully?

Hi folks, I get a problem on a specific Webstorm project with the new version of the plugin. (2020.2.0). When I clone the project from a remote Git repo and open it in Webstorm (2020.1.4), I get the NS menu when right-clicking a file, but there are no items in it, it just say "Nothing here". But when I got to the prefs for the plugin to add an environment, and add one, and then go back to the file and right-click it again, the NetSuite item in the menu has become grayed out and the icon has stoped working, looks like this, anyone else had this problem?

is it true that the suitecloud CLI and the webstoirm plugin have a common shared credentials store? I'm not seeing it between the latest? cli (v1.1.1) and the webstorm plugin (2020.2.0) - if I do a

suitecloud account:manageauth --list

it lists different accounts then the ones that show up in the webstorm plugin configuration UI

I was looking forward to being able to use either the plugin or the CLI freely without managing auth separately between the two tools?

Does SDF have an object representation of the GL Impact Customization script type?

@ExtendApps Inc.

customglplugin

Ok, I'll have a look. Strange it does have a Down XML option in the UI

I don't know if anyone else has experienced this but if I choose "update all objects with account objects" it updates the custtmpl_xxxx.xml but not the custtmpl_xxxxx.template.xml file. is this a bug or am I doing something wrong?

I'm trying to get a vendor bill form to pass SDF Node validation and have some errors like:- • Line No. 78 - Error Message: Invalid "id" reference key "CREDITLIMIT" • Line No. 801 - Error Message: Invalid "id" reference key "AMORTIZATIONSCHED". Some screen fields, some sublist fields, all native fields. The ids were the ones included in the Download XML and also pulling the object directly using SDF. Would anyone know why the ids are wrong?

I am using Webstorm for NS development. I am trying to open our 2 separate Sandboxes as a separate projects in one window so that I do not need to switch between windows. For this purpose I have attached the second project to the first one but when i click the dropdown arrow on the second project, it does not show any folder structure so that I can import the script files from second sandbox.

Has anyone successfully 'deployed' using gitlab's CI/CD using suitelcoud CLI?

I did @darrenhillconsulting

deployed and published as a bundle 😄

Getting this error...any help would be appreciated.

I'd be really interested in speaking to someone who has successfully deployed Transaction Forms using Node CLI - it seems to me that validation for node cli is slightly different to that of ide plugins. IE i have an .xml form file which passes validation in one but fails in other with exact same values. Would be great to hear from someone who's using cli extensively for wide range of objects

Open a case yourself? I don't know why people are hesitant to do so, it's there for a reason

Hello SDFers. If I

suitecloud project:package

then

suitecloud project:deploy

, does it use the pre-built package? In other words, I'm wondering how/if we can leverage

project:package

effectively.

I mean, if I can create a package ZIP, I should be able to hand that ZIP to some other system in order to easily deploy it, yes? Otherwise, what's the point of a standalone

project:package

command?

I'm in agreement @stalbert

As far as the 'caching' issues people saw where they were updating scripts, but NetSuite was running older versions ... did anyone figure out a workaround?