Olivier Gagnon NC Red Ribbon

You can use "anyof" in suitescript, even if you're only giving 1 value.

While this is fairly easy to do, I don't recommend you do this. It would be a better idea to keep this information as a Saved Search you can refer to, rather than sotring the number on the customer. The reason for this is that a Saved Search is dynamic, and so everytime you look at it, you are sure the information is…

You must use a nlobjForm (or nlobjList) as top-level container in order to have the NS look and feel. Check out p.226 of the dev guide for details on how to use nlobjForm.

Oliver, As far as I went through the suite script guide, we can set already existing items in the list using nlapiSetFieldValue() and nlapiSetFieldText(). Err... no. nlapiSetFieldValue() will not allow you to do what you are asking for, you're on the wrong track. You need to create your list on beforeLoad. Your beforeLoad…

If you want to stay within supported methodologies (not that you have to), to block a delete you could use this code: function beforeSubmit(type) { if(type=='delete') { var err = nlapiCreateError('INVALID_DELETE','You are not allowed to delete this record'); throw err; } }

Yes, you have to use a UI Object dynamically created list (a nlobjField object). You can then add or remove data with a client-side script.

Post your code

I'm not sure this answers your question, but Suitelet are display only, they do not store any information ever. You can use a Custom Record if you need to store values for later use.

var nlapiGetFieldValue('custrecord_returned'); var nlapiGetFieldValue('custrecord_date_returned'); var nlapiSetFieldValue('Custrecord_available'); you're missing the actual variable name in all three - i.e., should be something like var fubar = nlapiGetFieldValue('custrecord_returned'); if ('custrecord_returned'==TRUE &&…

Can you confirm this is a defect? This is a huge deal...

No. It will save and open a new Deployment for you to configure. It will not execute anything.

* You cannot use nlapiGetFieldValue() on afterSubmit * You have { }t hat don't seem to belong to anything. According to your comments, shouldn't there be an If there? * ( nlobjRecord.setFieldValue('custrecord_book_availab le'), 'F' ); this is wrong in several ways. You cannot actually use nlobjRecord, you have to…

I assume you are talking about a Scheduled Script. Have you read pages 58 to 65 of the dev guide? There is a lot to say about how Scheduled Scripts work, it'd be best if you start off by checking that out, and then if anything confuses you to post those questions.

nlapiRemoveLineItem(type, line) - page 141 of the dev guide Cheers

No, you are correct. If you want to try something a bit crazy...: Create a 'dummy' employee record (call him SYSTEM or something). This is the employee record that you will use for the "From" of nlapiSendEmail. Then, before you actually send the email, use a nlapiSubmitField() on 'email' to set the SYSTEM employee's email…

Yes, but mine refreshes with a CRTL+F5 key. I don't think you need to restart the browser, a hard refresh should do it.

You got upgraded to 2008.2 is my guess ;) I have noticed, but not spent the time to confirm, that nlapiRequestURL no longer works after 2008.2.

Hi, I highlighted in red potential problems - function DisplayAcctType() { try { //get account internal id var accountid = nlapiGetCurrentLineItemValue('line', 'account', null); alert(accountid); //this was displayed //filters var filters = new Array(); filters[0] = new nlobjSearchFilter('internalid', null, 'equalto',…

Can you post your code?

Run an nlapiSearchRecord() for transactions for the customer. No results = this is the first. Cheers!

To be clear, is it confirmed there is a OW bug that stops you from being able to correctly create transactions? I talked to support about this and they said nope, everything is A-OK. As with everyone else, this would be disastrous if this is true, so I need to know.

A few style points I would comment on: * Some of your variables are not declared with var. Always do this, even is JS doesn't force you too. I've seen scripts break because of this. * The "count to 6" thing is kinda weird. You'd probably be better off staying with booleans. You could do it like this: soautoapprove =…

Well, you could also just create the field through create new Transaction Column Field, setting up your sourcing there. In fact, unless you're in a situation where you HAVE to create fields through scripting, it is recommended you create them through the interface.

The deployments aren't a problem. There are plenty of deployments. It's a question of timing. If you call: nlapiScheduleScript(scriptA) nlapiScheduleScript(scriptA) nlapiScheduleScript(scriptA) nlapiScheduleScript(scriptB) will the actual execution be in the exact same order, or is there a chance scriptB will be executed…

You cannot call nlapiScheduleScript from a Scheduled Script. That is the cause of the error message. Cheers

You can do it manually. Use Save & Execute on your Scheduled Script deployment. You can stack as many as you want, they will all queue up and execute one after the other. If you need to do this programatically, when you call your nlapiScheduleScript (in User Event or client side) just call your script 2-3 times, or…

Go to your Script record in View mode Click on the Deployment tab Click on the record type the script is deployed to - This opens up the Deployment record. Edit it. On the permissions, make sure the All Roles checkbox is ticked in.

*smack forehead* Of course! Thanks yang, as always :)

I noticed this about a year ago. There's an Enhancement request somewhere for this - so yeah, basically, not supported by Netsuite.

Your post is not very clear, but I'm just going to focus on this: But I want to ask the user if they really want to perform this action. If they click "yes" or "ok", go ahead and perform the rest of the code. If they click "no" or "cancel", abort the script and the saving process so they can go back and uncheck the…