3941980 Green Ribbon

Amit, It does not appear to matter which shipping method is initially selected. I tried setting the initial ship method to 3 different values (1545, 3, 245) ... in each case, I was unable to change the value of the 'shippingcost' field. Typically, ship via would be set to 3 (UPS Ground - Cont. US Only) when first created…

'shippingcost' no longer appears in the list of 'cashsale' fields in the suitescript reference, however, we continue to successfully set the value of the 'shippingcost' field on a 'cashsale' in version 2007.0. Can someone from Netsuite please clarify what is going on here? Thanks, Dave

Yes, we are setting the 'shippingcost' field prior to submiting the sales order, as in the following: var so = nlapiLoadRecord('salesorder',id); var shippingCost = "1.37"; so.setFieldValue('shippingcost',shippingCost); nlapiSubmitRecord(so,false); Could you please clarify what it is that you mean by "overriding the…

There were also changes to the API that we had to deal with after going to 2007.0 ... From the error message you report, it looks like you'll need to change your code to accommodate for the way the nlapiLoadRecord behaves in the new version. Best, Dave

Thanks for your help, Amit. Best, Dave

Netsuite, Please refer to case # 568402 concerning this problem. Thanks, Dave

1. I have found that either scheduled or portlet scripts will generate the error. 2. Yes, it fails every time under the conditions described in my first post. 3. "Portlet Test" is a script that succinctly illustrates the problem. Thanks, Dave

I've submitted support case #526795 concerning the failed call to nlapiSubmitRecord(...).

You might want to have a talk with QA ... I spent quite some time on the phone with support detailing how we narrowed the issue down to the call to nlapiSubmitRecord and QA responded by instructing us in the proper use of the nlapiLogExecution function ... yes, when you look back through the log there was one occasion…

Yang, Is there a reason that v11.0.6 is requiring a recalcuation of shipping cost on a call to nlapiSubmitRecord(...)? Is there a way to recalculate shipping cost via SuiteScript prior to submitting a record? In our efforts to troublshoot this issue we mananged to generate the following stack trace: Stack Trace:…

Issue 118558 - Call to nlapiSubmitRecord(...) fails Thanks again for your efforts. Dave

Hi Mini & Yang .... Thanks for your efforts. We still have one server script that fails ... I've narrowed it down to a call to nlapiSubmitRecord(...) regardless of whether the 'source' is set to 'true' or 'false', This was working fine prior to 11.0.6. Unfortunately there is no detailed information reported with this error…

The last scheduled server SuiteScript that executed successfully for us was at 11 am yesterday (Sunday, 11/19/2006 EST). Every script since then is now "In Queue." Nothing is executing. Any information that would shed light on what is going on with Netsuite server script execution would be greatly appreciated. Thanks, Dave

Yes, Yang, I'm catching the error ... getDetails() returns 'null' and the following stack trace: [Ljava.lang.String;@52d03c6 Not much to go on ... does this tell you anything? Any other ideas on how to debug this one? Thanks, Dave

Jan ... Any luck getting this function to work? We are getting an exception thrown (an error object with no details) when simply specifying template id, 'customer', and the customer id as the first 3 parameters. My best guess at this point is that this function allows for pulling information from two different record types…

We also have a deployment that is caught in a perpetual 'in progress' state. The move to 11.0.4 botched a perfectly fine scheduled server script. To get around it, we simply created a new deployment and continued on our merry way. It does not appear to be negatively affecting our account, but it is an annoyance. Can anyone…

Yang, the error codes and details are infinitely more helpful when passing *invalid* id's: Code: SSS_INVALID_EMAIL_TEMPLATE...Details: That e-mail template is invalid, disabled, or no longer exists. Please select an active e-mail template Code: RCRD_DSNT_EXIST...Details: That record does not exist. We are passing…

Yang, The error code isn't of much help either: UNEXPECTED_ERROR. The script is definitely failing on the call to nlapiMergeEmail(17,'customer',1234) regardless of whether I'm specifying one or two record types and regardless of whether the email template contains tags requiring data from the supplied record types. Thanks…

Hi Yang ... thanks for your response. Advanced Shipping has been enabled all along. All orders that we are attempting to bill out with this scheduled script have the pending billing status. Could you elaborate on what it means to be an injection? Any ideas for a work around? What property of the record object associates…

Yang, thanks for the heads up about the API template. Seems that our original server script issues since 11.0.3 have gone away ... perhaps thanks to the fixes that were pushed out on Tues. night? On Tues. afternoon we were simply getting "Scripted content: An unexpected error occurred." where nothing showed up in the…

Hi Yang ... The latest SSS developer documentation available from help still demonstrates the old API under CRM Use Cases. What we really need to have working again are our scheduled scripts which broke since 11.0.3. Given that the develop docs are not up-to-date, is there some other location you can point to where we can…

Regarding the nlapiTransformRecord(...) issue, we've submitted support case #458188. Thanks for your prompt attention. Dave

Thanks, Evan ... the enhancement request is #454579. Regards, Dave

Hi Jan ... When you say it does not get set, are you referring to the SuiteScript record object or the actual value in the sales order? If you are able to see that it gets set in the SuiteScript record object, you might take a look at the "source" argument to the nalapiSubmitRecord(...) function. We have found that when…

Thanks, Yang ... So, if I understand your explanation of "sourcing" correctly, it seems that it shouldn't interfere with the proper population of the unit and item option fields when submitting a cash sale or invoice record created as a result of a transformation from a sales order and perhaps this is one of the issues…

Hi Elham, Thanks for looking into this as soon as possible. Since my last post, our scripts have been generating errors when attempting to submit a cash sale or invoice record that has been created by transforming a sales order that contains items with required item options. It appears that the transformation process is…

Hi Ray, I have not seen any reference to charging by the unit for the execution of Server SuiteScript. Is Netsuite really lumping SuiteScript under the umbrella of "Web Services?" The Server SuiteScript developer guide simply refers to the following "governance" ... In order to optimize Netsuite application and database…

Hi Yang, thanks for your note. Could you elaborate on what sourcing is meant to accomplish? ... The info in the dev guide is a bit sparse. We are finding that with sourcing turned off (source set to false) that all of the relevant data is moving just fine from the sales order to either a cash sale or invoice. Where exactly…

Problem solved. It's now working correctly as long as the the "source" argument to nlapiSubmitRecord(...) is set to false. Best, Dave

Hi Wayne, I appreciate your help ... seems that there ought to be a less cumbersome approach to development, however, your suggestion works and will do for now ... can anyone from Netsuite comment on SuiteScript development methodology ... namely the pre-deployment testing of scripts? Best, Dave