Olivier Gagnon NC Red Ribbon

You should be able to simply call nlapiSearchRecord to find the data you're looking for. To make things easy, as you're not a programmer, you can create the Saved Search that returns your data straight through the normal saved search creation UI, and simply have the API reference your saved search ID as the second parameter

There is a client script caching issue. I believe it is scheduled to be resolved next week or so.

Yeah, a beforeLoad script will do nicely.

For the triggerring, you'll probably want to put this on postSourcing of the 'item' field as well.

You want to do this in a webstore, or within your Netsuite account?

I received a notice that this issue should now be fixed.

You would need a small Web Services middleware app. There is absolutely no way to do this using suitescript, as for obvious security reasons web sites cannot write to computers.

Browsers cannot automatically output to printers, again, for security reasons. Middleware app can do this as well.

Right, that error points to the fact your script isn't properly deployed. Aside from that, the code wouldn't work anyway. This "nlapiLookupField('account', 'custrecord1');" won't work. Checkl out the API documentation to see how to use the parameters of this function. While this should not stop correct execution, your…

To explicit this - you need a beforeLoad script to display the button. That button must call a Client-side script. While I pshah's script below method of attaching the client-side script probably works, this is more normally done via the supported methodology of the form.setScript() function. You can check out how that…

What does "customscript_sdr_ss_case_replytoall" point to? What kind of script record? It should be client-side.

This is an ongoing problem since version 2010.2, so couple months now. Client-side scripts get cached and the old version sticks for until cache is cleared overnight. Please file a case to help improve the pressure to get a fix. In the meantime, you have to rename your .js every upload so NS recognises it as a new file so…

Ah ha! Found it. Here is the formula we used: {rate}*{quantity}/{quantityuom} Stick that in a formula and let me know if that works.

Suitescript cannot upload via FTP. You'll need some sort of middleware to perform this task using SuiteTalk.

I tried fiddling with this a while back. I don't remember the exact scenario now, but I either could not get the rate with UOM factored in, or it was always factoring with the wrong UOM, or something like that. I was a HUGE pain. I think recently we fiddled with it again, and was only able to extract the correct…

1. add button in view mode using beforeLoad 2. attach script to record using form.setScript in same beforeLoad 3. button calls script from attached script 4. ??? 5. Profit

yeah, you can do that. Call a Contact search, filtering on the customer internal id, and output that checkbox. Loop through the search results and write to the To Be Emailed box. Make sure to do this beforeSubmit (and not afterSubmit) because the email is sent at a point between before and after submit. Of course, don't…

That is correct. To CLOSE an order, you must close each line (via the field 'isclosed' set to 'T'). Not that, when you use the yellow Close button on the UI, it actually does this exact thing. Note that this is for CLOSING orders, not CANCELLING them. Not quite the same. You cancel an unapproved order, you close an…

On a SO, or on the webstore front-end? And what do you mean by "clear" the online price? Do you mean set it to Base Price?

Beat you to it by 3 years yang ;)

Scheduled script that create records causes said record to trigger it's User Event scripts. So you can either have the logic directly in the scheduled script, or have it as a UE script on the Invoice. Basically same thing.

Do you use multi-location?

Client side scripts are NOT triggered by nlapiCreateRecord / nlapiSubmitRecord You will need to recode your logic as UE script so it fires.

By default javascript treats all additions as string concatenation (since it's not a typefied language you can't really blame it). As point out, always cast your numerical values with parseInt() or parseFloat() before adding them or even comparing them (to avoid alphanumerical compare)

Hey Peter, You can't specify an email, you do have to use an Employee, BUT that employee does NOT need to have access to Netsuite. A dummy employee record will do fine and that does not require any license on your part.

If you were able to set the value of an existing price level, that was basically postive exploitation of a bug. You should never have been able to.

What do you mean by authenticate? Authenticate thye user? Are you talking about actual NS Web Services or do you mean you've created a Suitelet which acts as a simple WS interface?

Can you try: recSalesOrder.setCurrentLineItemText('item', 'price', -1); //set to custom recSalesOrder.setCurrentLineItemValue('item', 'rate', stItemRate)

Yeah, we've really been scratching our heads on this, and it has caused a lot of problems with clients. The problem persists across all the browsers we use (Chrome, IE, Firefox) and it's happenned on multiple accounts.

Hmm, haven't really tested bundles. Can only confirm we're seeing it for stuff dropped in the file cabinet. Your explanation makes sense, I hope you're on the right track cause this is becoming more and more a problem.