Olivier Gagnon NC Red Ribbon

1) nlapiLookupField is cheaper to use in terms of metering as well as processing time, so when possible, it should be prefered over nlapiLoadRecord for the purpose of reading fields. HOWEVER, nlapiLookupField does not work with transactions at all, and some fields are simply not exposed through nlapiLookupField, but can be…

That is only in regards to beforeLoad User Event scripts, so it does not apply to your script. There's nothing wrong with that you are trying to do, aside for the potential problem that 'entity' may sometimes be empty.

How have you ever been able to run that? It is wrong. You can't do var Customer = nlapiGetFieldValue('entity'); var Taxable = Customer.getFieldValue('taxable'); you have to do var Customer = nlapiGetFieldValue('entity'); var custRecord = nlapiLoadRecord('customer',Customer); var Taxable =…

Are you trying to change the description on the Item record or on a Purchase Order?

Recalc should fire if you remove a line, I think.

I'm trying to set shippingcost to 0 in a beforeSubmit script, using nlapiSetFieldValue() and it seems to not be working... Is there still an issue with with beforeSubmit script trying to set the value of shippingcost?

You would need to use nlapiSendEmail(). Create your email, then send it. The downside is that you'll need to turn off automatic emailing of confirmation, and then write another script to snd out emails in a regular situation.

Hi David, It is true you cannot set shipping cost. I think it was mentionned in another thread this is a bug. But I don't think it will be fixed quickly. In the meantime, there is a "hack" you can use to set your shipping cost value by bypassing the Netsuite APIs and playing with the code directly. Just paste this into…

Hi Kate, I just checked under Help->User Guides, and the both the dev guide and reference guides are dated well before March. Dev guide is Dec. 12th and Ref guide is Jan 9th. So... where are these bi-weekly revised guides you speak of?

Interesting, I was just speaking with our Implementation guide about this. We would also like to send out an automated survey after the order has been fulfilled. Please email me also, curious to whats involved. Thanks. If you want to send a email immediately after the order is fulfilled, you can always do this using the…

Hi, You can embed the username/password field you would normally find under netsuite.com into any web page. Just paste the following code into your HTML: <div id="homelogin"> <form action="https://system.netsuite.com/app/login/nllogin.nl?ck=GMpVea7wAFGn8B8D&vid=RlL30X_wABoRx1nF&cktime=1614" method="POST"> <p…

Hi, We are Netsuite Partners, and this is right up our alley. I have sent you an email with my contact information (which is also in my signature below). Cheers

Yeah I was looking at that just the other day, too. It really is a boolean though. The example given is accurate.

Sorry, didn't mean invasive in reference to privacy. I meant in terms of mechanics. You'd need to have a lot of scripting catching user logins and redirecting them to Netsuite login, then catching unsuccessful logins, etc. "Complicated" is probably the word I should have used. I don't see any privacy concerns off the bat.

This may also be done without scripting in 2008.1 using saved search e-mails. Thanks, -e Hi Evan, Is it possible in 2008.1 to send Email Alerts to Entities such as Customers that do not necessarely have a Customer Center access? I think that is the current limitation. Otherwise, I think we would be able to use the dynamic…

Hmm, no, never did anything that invasive, sorry.

We had a similar situation. We created a fake employee (AAA System) with the email of system@ourdomain.com. Not pretty but it works. Best regards, Yeah, that's what I ended up doing too. I take it that the documentation is wrong (or badly written) and that you can't "default to script ID"...

To answer one of your questions: Valued do not store in script created fields - you would need to write to a 'real' hidden field On Save, and then On Load write it back into your created field.

Should be something like: var searchColumns = new Array(); searchColumns[0] = new nlobjSearchColumn('salesteammember',null); searchColumns[1] = new nlobjSearchColumn('contribution',null); var results = nlapiSearchRecord('transaction',TRAN_ID_HERE,null,searchColumns); if(results!=null) { for(i=0;i<results.length;i++) {…

Thanks Evan!

Right, I need to see several transaction types at a time.

'vendor' singular, not 'vendors'. Friday afternoon mistake my friend!

a little pseudo code here (don't paste this directly!) var record = nlapiCreateRecord('journalentry') record.setLineItemValue('line','account', linenum, yourCogAccountId) record.setLineItemValue('line',['debit' or 'credit'], linenum, yourAmount) record.setLineItemValue('line', [department, class, location], linenum, value)…

Hmm... What is in the variable lines? lines = nlapiGetLineItemCount('item')? Also, you should not use nlapiRemoveLineItem('item',i). You should put 1. Reason being removing lines screws around with your index position. So cycle through i=1 to line item count, but stay at 1, if you know what i mean. var lines =…

Hmm, never tried doing anything like this, but looking at the dev guide, perhaps you are looking for: • “nlapiRequestURL(url, postdata, headers, callback)” on page 94 or • “nlapiResolveURL(type, identifier, id, editmode)” on page 96

At this point, I would just move the script to after submit and go with var record = nlapiLoadRecord(nlapiGetRecordType(), nlapiGetRecordId()); var size = record.getLineItemCount('item'); for(i=1;i<=size;i++) { record.removeLineItem('item',1); } nlapiSubmitRecord(record,true);

You could do it on page save, but then you'll have to deal with asynchronous line updates if you need to modify more than one line, so keep that in mind. If memory serves, you can also do it on validate Line, which is after Netsuite does its Amount calculation, so you can overwrite it safely then.

Automatically can happen with scripting. So yes, Amy, what you want can be done with scripting. As to where to start... are you intending to write this yourself? Do you have programming experience? If you are set on doing it yourself, go in the guide section and read the suitescript developer's guide and download the…

Tried that, which got me a: TypeError: Cannot read property "length" from null (afterSubmit#59) So then I tried comparing it to null, which worked... I dunno, seems to me comparing to '' worked before, no? Does it still work? I have tons of scripts that do that...

Are you callng nlapiSubmitRecord on your modified record?