Olivier Gagnon NC Red Ribbon

Hi Olivier, [...] Do I have to include all of the inputs in the new suitelet URL that is re-called by the submit button? Yup. Note that, if it's easier, you can also use nlapiRequestURL(url, param) Where param is a parameter that will be fed to the URL by a POST rather than a GET. Otherwise, yeah, just feed everything you…

For OneWorld (actually, in any instance where you have taxes in multiple Nexuses (Nexi??)) there is no Tax Rate, only Tax Schedule. A Tax Schedule is a definition of what tas rate to use in what Nexus.

I think you'll need to fire off a Contact search, with a filter that you are looking for contacts that belong to this customer.

You need to add break after each end of case otherwise it cycles through each one. Check online javascript references for details

Lenght has always been correct for me. What do you mean by you use "system notes" to show you the length? Do you mean you use nlapiLogExecution() to output results.length ? Is this when using nlapiSearchRecords() by calling directly an existing saved search, or when you create all your filters and columns directly in…

Are you able to Fulfill your SO in the user interface?

Where is id coming from? Are you sure it's not the Fulfillment that is failing? Also, in my experience, it basically never happens that you can transfrom a record without having to change some values on it before submitting. There are many possible points of failure in your script. I recommend you break it down and debug…

Hmm, what do you mean by 100 records left out of 200? I assume you are using the results of a search to feed a process of some sort. Can you post the code you're using?

So this is on the On Save client-side trigger?

How are you executing this script? Client-side or User Event? What is your trigger?

I don't see any problems. I think you're gonna have to open a Case. If you want to do some debugging yourself, try just placing a script that returns false. Nothing else, just funciton onSave(){ return false; } and see if you get an unexpected error. Hmm, just had a thought - do you have any other scripts running?

Aha, though so. In User Event you don't need to worry about synchronous or fieldfire. You also don't need to commit lines. After setting the Amount on each line, you must also *manually* recalculate and set all your totals - subtotal, tax totals, total, etc, otherwise you will get an unexpected error.

var repId = tranSearch[i].getValue('internalid','salesrep','max'); i.e. .getValue(FIELD, JOIN, GROUPING)

If it helps you find a problem, if you have 2 different script with the same trigger function names (i.e. onSave() and onSave()), Netsuite goes berserk and does a cross product call, basically calling each function twice. That usually causes problems.

No, I meant you have to add all the recalculation code in your script, i.e. Netsuite will not do it for you.

No, you are no longer on the client machine, you are running code on Netsuite's server. There is no one to send an alert to. You can send an email, that's about it.

The Approve trigger does not return any values for fields. You will have to do an nlapiLoadRecord() and go fetch your fields this way,

Where are the variables id and userId being populated?

Try using nlapiLoadRecord, set the field, and nlapiSubmitRecord nlapiSubmitField does not work for Transaction line items (which Time entry are considered to be - don't ask) as well as some body fields. Not terribly reliable.

How are you populating the priceLvl variable?

YEs you can. Like discussed in this thread, there are certain gotchas. Time entries are an odditity in that they are both line items as well as body fields - depending on if you do weekly time entry or the "regular" time entry (weekly = line item). Otherwise, you can affect them normally.

You need different code for Weekly and normal. Weekly are line items and normal is not. That may be causing problems

If you pass an array to a function, it stays as an array. Your code snippet doesn't show how you pass it to the other function. Can you post the rest of the code? I do see that you don't declare your i inside your for. This is VERY dangerous. You should always declare your variable, i.e. for(var i=0; i<whatever; i++)

Are you working with the Weekly Time Entry, or the Time Entry?

function GetEvent(type) //before submit { if (type = 'delete') { var EventID = nlapiGetFieldValue('custrecord_support_event'); //get linked event to delete } } function DeleteEventRecord(type) //after submit { if (type = 'delete') { nlapiDeleteRecord('calendarevent',EventID); //delete linked event } } In this case, you can…

you can use nlapiSendEmail with a textual email address, so it shouldn't matter if it's the anonymous customer or not. The sender needs to be a valid user, but the recipient can be any written string.

beforeLoad is the wrong trigger. BeforeLoad is still a server-side call, so you cannot trigger live events on the user's screen. Move your script to a client-side pageInit.

nlapiGetNewRecord() returns a read-only record. Move your script to beforeSubmit and simply do nlapiGetFieldValue() and nlapiSetFieldValue().

I think so. Try record.setFieldValue('customform',CUSTOM_FORM) CUSTOM_FORM being the internal id of your form.

Your usage of nlapiLookupField is incorrect. Refer to the documentation for proper usage of parameters. It should be nlapiLookupField([recordtype], [recordid], [fields to retrieve]); i.e. nlapiLookupField('customer', nlapiGetFieldValue('entity'), 'custentityaccountingemail'); Cheers