Olivier Gagnon NC Red Ribbon

Yes, typically through a Suitelet for the server-side content.

Hello, As documented, nlapiRequestURL does not allow asynchronicity in user event scripts. There is no work-around that I know of, sorry.

Lorne, It is possible that logs are kept for 30 days OR until a certain amount of log lines are hit? For very verbose logs, we usually see only 3-5 days kept.

Use nlapiExchangeRate(sourceCurrency, targetCurrency, effectiveDate)

Use a boolean to control execution. Set it to FALSE at the beginning of insertSystemDiscount and set it to TRUE as the last instruction. Then, in onClientValidateLine, start with if(boolean). Since you've set it to false, you will exit your function and keep going with insertSystemDiscount.

Yup, now that you've got your custom record, check out this topic in the Help: SuiteCloud (Customization, Scripting, and Web Services) : SuiteScript : SuiteScript Reference : Scriptable Sublists : Custom Child Record Sublists

I think you have a red herring, I don't think the problem is this code. What is the Suitelet code?

A word of caution on that: the Ext JS library included in Netsuite is not officially supported. Netsuite could take it away or change version without prior notice (and probably will at some point). Do not build any enterprise-critical functionality using it. A safer approach is to upload the required Ext JS (whatever…

It seems the Suitelet serves no actual purpose, since you generate the PDF but then do not display it, you just want to redirect back to the quote. If you don't want to display the PDF, scrap your entire suitelet and move the xml to pdf code into afterSubmit of your quote. It'll reduce a lot of complexity you frankly don't…

Yes, create a custom record. You can look that up under SuiteCloud (Customization, Scripting, and Web Services) : SuiteBuilder (Customization) : Custom Records : Creating Custom Record Types in the Help.

Yes, check out the documentation for nlapiInsertSelectOption() and nlapiRemoveSelectOption()

Are you using a External suitelet? Any search called client-side will execute with local permissions. For an external suitelet, this means, well, none.

Hi David, I don't recommend using DOM manipulation to remove buttons from NS. These unsupported scripts are prone to breaking out of the blue as NS makes little changes to their UI. What I would recommend focusing on is rather putting Before Load scripts on subsequent transactions. These scripts would run verifications…

How are you uploading? is it an FTP? A form submission?

No it is not

There is no way to create sourced fields. You must code the client-side behaviour to do this yourself. i.e. on fieldChange of a certain field remove all values from target dropdown figure out what the new values should be (call a search maybe) add all the values back into the dropdown

This nlapiGetFieldValue ('type', 'systemnotes'); Is also an invalid instruction. nlapiGetFieldValue() takes a single value, the field being read. In this particular case, you're trying to read system notes, which can't be done this way. However, you don't need to do it this way, so that works out well. Create a User Event…

Which is what, exactly?

You are most likely getting dups from things like multiple locations or vendors. What columns are you exposing in your search?

Are you returning "Location On Hand" or "On Hand"? Are you returning "Location" or "Inventory Location"? Did you add a filter to take out items that are Inactive?

You almost always use getFieldValue(). getFieldText() is used exclusively to return the text value of a dropdown (whereas getFieldValue() returns the internal id of said dropdown value)

Hello This is normal behaviour. When "To Be Emailed" is ticked in prior to save, upon saving NS will perform the email, and then UNTICK the box. This occurs because NS emails every time you save with the box ticked in. Hence, if NS left it ticked in, it would constantly be emailing, which is probably not what most people…

It could happen, yes. So, say you have your script deployed on SOs and you CSV import 100 SOs. Each SO will fire off an independant execution thread. There will be a slight delay between each trigger (the time a SO takes to get created), but this could certainly lead to a first SO making a query and then a second SO making…

I can't think of any way that would work, though admitedly I've never thought about trying to do this. There's no API I can think of though.

I don't recommend doing that. Messing with the UI in any way other than what is supported by the Netsuite API is asking for trouble on the long term.

Use .getFieldValue() and .getLineItemValue() instead Cheers

Oh, I see what you mean. Like if a Suitelet edits a customer and that customer has UE scripts, the context would say 'suitelet' but you're saying you would want to know "this is a UE" But... I mean, this wouldn't change, no? A UE script is by definition a UE script, there is no ambiguity, unless you're reusing functions,…

No results were found. In this example, it's because ''_salesorder'' is not a valid type. I'd just change the code to remove that filter altogether have the search call be var results = nlapiSearchRecord('salesorder', null, null, columns);

Hi Julie You are missing nlapiSubmitRecord()

There should be a message in the Communication tab, yes. Are you on a Sandbox? Is there a valid email address provided? Is your SO approved (does not email if not approved)? These things would cause problems sending out the email.