Olivier Gagnon NC Red Ribbon

Yes, you'll simply need to build a scheduled script with a loop built around nlapiDetachRecord(). You can check the documentation for details on that API. Not sure about enforcing a single attachement at this time.

Where is the 'verified' field? On the Phone Call or on the original Suitelet?

Ok... you're gonna have to detail how this all comes together. My guess is your solution architecture can be steamlined to avoid this issue altogether

Hmm, I think nlapiGetContext().getExecutionContext() is what you're looking for

After Submit will not trigger other UE scripts. Your Case script would need to ping a Suitelet to create the Opportunity record. That would trigger the Opportunity scripts. This is fine as long as you're not extremely high volume.

1- If I call a suitelet from a user event script, does the time governance on the user event continue to run until the suitelet has finished executing? Yes. Using nlapiRequestURL() is synchronous in UE. Your UE line execution will thus halt and wait for the Suitelet to return a response before continuing execution. After x…

No, I can confirm you must deploy on all related records. Nothing on the PO will detect the change.

What if you full use case? It is not typically recommended to create records in client-side, can't you move your code to afterSubmit?

Check the documentation for nlobjSearchResultSet and getResults(start, end) method

The message text itself? Probably a little too long for a GET param, but you can use a POST. Or pass it the internal id of the Message record so the Suitelet can load it for itself and retrieve the message.

10 executions, as the UEs will indeed execute in parallell.

You could reduce all this code to 1 line. Since you're using an existing saved search, just to a window.open on its URL. Add that quote filter thingy as a footer filter, and observe the URL when you give it a value. The value appears as a GET param, so your script can paste the correct value in the URL and just open it. No…

Has anyone had any experience in adding controls on number of running suitelets? You'll get an error upon your nlapiRequestURL(), so you could wrap that in a try/catch and keep trying till it works. No other way to handle it, there is nowhere you can see what the current load is. As well, there no add-on that a customer…

Check out the documentation section on SuiteTalk (Web Services) or the section relating to RESTlets and Suitelets.

Hello, I am trying to pass an array of rows into a suitelet but am having difficulty. I can pass a single row in by using individual parameters but I have multiple rows and am putting them into an array object, e.g. var resultsJSON = { record:[] }; resultsJSON.record[x] = [var1, var2, var3] // adding multiple rows var Url…

Ok. You might try filing a Case for that warning message. From memory, I believe those are sometimes blocking and sometimes non-blocking. *shrug*. Maybe it's not supposed to be blocking. In any case, there's 2 things I can think of - First and easiest, try messing with the 'recordmode' variable, putting it to 'dynamic' to…

Per line taxes is turned off Ah, that's why. I was thinking of per-line taxes. Yeah, looks fine. You have a pretty simple scenario so this looks alright.

err = null I guess. Never tried that.

You'll have to check the System Notes. So long as the line wasn't 0$, there will be a GL Impact / Total change in the system notes. However, that won't tell you exactly what happened, as deciphering line items by their GL impact is sometimes difficult if not impossible. If you need very precise reporting often, I would use…

Item type is a default field already on sublists. It is hidden, but it's there. No need for a custom column.

Coincidentally, we ran into this just last week. Turn out Error object cannot be serialized by Yield. Yield feels it needs to serialize everything, can't serialize error object, failure. The only "work around" we found was not to have any try/catch. Kind of not a great way to do things. Worst case you can not use Yield and…

Does this work? I did not think it was possible to write to 'taxrate' directly. What are you using as tax code?

If it's a purely javascript error, it is not an instance of the Netsuite error object.

nlapiGetContext().getFeature('DEPARTMENTS'); See the API for more details

Hi Olivier, Is it possible to do show alert message from user event? As far as I know, user event cannot show alert message. CMIIW thanks You can post non-interractive messages by throwing an error, something like beforeSubmit(type){ if(condition where you don't want to close){ throw nlapiCreateError('CANNOT_CLOSE','You…

Unfortunately this would not work, as pressing the "Close" button will not trigger any client-side events. You would need to run the code as a User Event

Right, that is what you would do. Call a search, get your results, and add them to the dropdown using nlapiInsertSelectOption.

Hi, Check the documentation for the nlapiInsertSelectOption(fldnam, value, text, selected) API. It should give you a good starting point. Note the very important notice about the fact that you can only use this on objects you created by script.

Where is this script deployed, exactly? How is this triggered? var itemDetails = nlapiSearchRecord('salesorder') This variable is never used, get rid of it, it's going to kill your performance for no reason "sagepaydirectpro" - is that literaly what is written in your Payment Method? Seems unlikely, but it's not…

To a certain extent, you can alter the content of a dropdown by setting values under the Sourcing&Filtering tab. What you are describing however seems too complex for that functionality. Give it a shot, but I think you'll probably need to turn to scripting.