This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

ok so are customforms not really supported by SDF?
• there is no form option in the new object dialog (webstorm plugin)
• when i import with webstorm or node cli i get the same answer but node does not validate exactly what it imported.. when i fix that then webstorm doesnt validate it.  cannot get them to agree about a form.
• the silliest error is related to the `standard` attribute of the top level `entryform` tag. 
```&lt;entryForm scriptid="custform_tst_recorda" standard="STANDARDCUSTOMRECORD_TST_RECORDAFORM"&gt;
.
.
.
Line No. 1 - Error Message: The attribute "standard" has an invalid value. The expected values are the following - "STANDARDSCRIPTID=CUSTOMRECORD_TST_RECORDAFORM".```

<@UFUCXSXCJ> so this is definitely a few bugs in either the webstorm plugin or node cli or documentation or all of the above related to custom forms.   My guess is that when they are having trouble interpreting the form they somehow default to requiring SUBSCRIPTIONGBILLING as a required feature.

1. The docs says that the `standard` attribute of `entryForm` is option. But it is not option according to the SDF tools: 
```Validation failed.

An error occurred during custom object validation. (custform_tst_recorda)
Details: The entryForm field requires the standard attribute.```
2. Further, both webstorm plugin and node cli are interpreting this form as needing the SUBSCRIPTIONBILLING feature eventhough it is of type `STANDARDCUSTOMRECORDFORM`

3. The error message in node cli and webstorm tell you differently in how to populate the value of this field. The webstorm one is correct and node is incorrect. incorrect shown
```
    - Line No. 1 - Error Message: The attribute "standard" has an invalid value. The expected values are the following - "STANDARDSCRIPTID=CUSTOMRECORD_TST_RECORDAFORM".```

In node cli, there are some known issues with local validate for cust forms. The error you are mentioning for node cli is definitely `local validate`
If you validate against server, you will get the same error as in webstorm. Can you please try

that seems to work.  another bug would be that local validate message says that it is validating against the server (even though it isn’t)

what do you think about those other bugs?