Olivier Gagnon NC Red Ribbon

Oops sorry I missed this. Just by looking at it, I can't see what the problem is. The code looks sound. Might be a deployment error. Hard to say without looking at it in your account.

Unless that's a copy/paste type, you forgot to put quotation marks around item alert(nlapiGetLineItemCount('item'));

There is no instruction-based governance, so no need to verify it.

Yeah we constantly hit this limit too. Seems to be a case of incorrect documentation. At least with multiple libraries, it's possible to create a consolidated script.

Here's a completely theoretical idea I haven't tried - I noticed that in Saved Searches, you now have the option to set it as a Reminder. So say you have a reminder search for a custom record type, you could create one of these "reminder" records so that it appears in the user's list. The user would then have a reminder…

function onSave() { var status = nlapiGetFieldText('custentity6') if ( (status == "In Progress")) { alert ("Please enter a Pilot Expiry Date"); return false; } return true; } I can confirm the rest is possible with scripting

Mhm. Several problems. We're going to have to scrap what you have here, but I'm going to correct it just so you learn a bit - (numbers are line numbers I will refer to) 1. function FieldChanged(type, name) 2. var status = nlapiGetFieldText('entitystatus') 3. var reason = nlapiGetFieldText('custentity_reason_closed_field')…

In your Ifs, just also check if the form you are currently on is the form you should be on. If it is, do nothing.

Yeah, you got it. Mainline = T does not work well with Journals - try it in the UI, you'll see. I don't remember off the top of my head what works. Try messing around in the UI and see what you get. Might be mainline=F, or maybe you have to use some other filter. I know it's possible.

Serial Number records will be scriptable starting 2011.2 - so very soon! I intend to have a party to celebrate that, fo shizzle.

I was running some yesterday and then all went well. These types of queue problems are often account-specific.

;) Cheers

According to the Ref guide, currency is a searchable record. Therefore, it does look like you could simply call nlapiLookupField('currency',Id, 'exchangerate') where Id is the internal id of your currency.

yes, the syntax is simply [baseurl]?param1=value&param2=value so just seperate param=value groups by the ampersand ("&") symbol

Hmm... Here is an idea for another direction. Have your POST create a custom record, and afterSubmit of that custom record you call nlapiScheduleScript(). In nlapiScheduleScript, you have code that adds the customer record's item to the SO. Scheduled Scripts fall in a straight queue, so there would be no possibility or I/O…

It's all just one big string, so you have to put the quotation marks correctly - location.href=(nlapiResolveURL('SUITELET',8,1) +'&ContractRecordID='+CurrentContractID+'&ActionID=Print');

Ouch. I don't know if you'll be able to do that... If you're really desperate, you can create a dummy transaction (like a SO for a dummy item), set the date you want, save it (therefire letting NS set the exchange rate) then read the exchange rate off of it. Then delete the SO. Technically, it'll only cost you 20 units to…

No, it is not, sorry. I believe I opened an Enhancement for this years ago - if you can find, you can add a vote to it.

Unless you want the script to very specifically run on certain forms, you should use a Record-Level Client script. These can be run in Testing mode, which greatly simplifies things. Refer to page 83 of the dev guide for more details on the difference between record-level and form-level client scripts.

What Yang said. Basically, replace var record = nlapiGetNewRecord(); with var record = nlapiLoadRecord(nlapiGetRecordType(), nlapiGetRecordId());

Hey Bushra, Try using 'newquantity' instead. Cheers

Just to speculate, but those might be booleans

That's a non-Netsuite field. I am guessing he added an inline HTML field and created the field from scratch himself in by adding the correct HTML tags.

Suitescript does not allow you to break normal NS rules. Like, you wouldn't be able to script an SO and an Invoice with different customers and have the createdFrom link to each other. You wouldn't be able to script an Invoice that is createdFrom 2 sales orders, etc. So as I said, because a PO can only ever be createdFrom…

I have, and can assure you others have as well, created POs from scripting before. So there is no global issue blocking you - just probably something wrong or missing. No bid deal - we can figure it out! I'd start out with Yang's suggestion - you shouldn't be setting currency. Also wrap your code in a try catch with an…

You can NEVER set a value for created from. A PO can only be created from an SO for Special Order or Drop Ship items. So you will have to follow that flow to have your PO's createdfrom to point to your SO.

Does this thread help?

I believe it is 'orderstatus'

According to the Reference Guide Checks seem to be supported, though I haven't tried to code one in a while. Can you post your code?

If memory serves, A is pending approval B is pending fulfillment