Hmm, good question. I'm not sure what is causing the cursor to go to the line items. Try placing it in pageInit(). You could also try right after you do your nlapiSet...() but then it'll refocus to the customer every time those fields are changed

Yup, you'd fire a search. That little sublist cannot be read, but a search should work very well.

Hmm, think you'll need to use good ol' DOM to reset the focus to the customer. Something like - document.getElementById('entity').focus()

Have you tried using a Saved Search Alert? You should be able to set it up to send emails when new records are created. Using Dynamic Recipients, you should be able to specify the email entered on the custom record.

Remove the ; immediatly after your if() statement and remove one of your closing } Code should thus be: if (nlapiGetFieldValue('custbody2') == 1) { nlapiSetFieldValue('shipmethod',1144); } Cheers

Yeah that ought to be pretty easy. I can conceive of a couple ways of doing this. It kind of depends how you want to differenciate employees from group A vs employees from group B. Technically speaking, the easiest way might be to just add a checkbox on the Employee record "Requires SO Approval". But if you want to to work…

Help->User Guides->SuiteScript Developer Guide Be warned that scripting is not easy and is best done by someone with a programming background. To get you started, you'd want to code something close to: function beforeLoad() { var role = nlapiGetRole(); if(role==XXX) { throw nlapiCreateError('PERMISSION_VIOLATION','Your…

function pageInit(type) { if(type=='create') { nlapiSetFieldValue('fieldname','F'); } } If you replace 'fieldname' above with the actual internal id of the Integrated Shipping Label field, this code will uncheck the box by default when a Fulfillment is first created. Was that what you wanted?

Ah yes, I had a client talk to be about this some time ago. Basically, there is no totally satisfactory way of doing this. To restrict vendors, well, the person must have View rights to see the ones they are supposed to see. But that grants them everything. So what can you do? You can remove the ability to run searches and…

No. What are you trying to do?

Why do your RMA have no Created From? How are you creating them? Are you pressing the yellow button on the SO? In 'After Submit Function' I have entered afterSubmit but nothing else. This is correct.

The field name is probably in lowercaps, so make sure the caps are correct (it makes a difference). The function name shold also be pageInit, not PageInit. Otherwise yeah, what you did sounds correct.

Hmm, it's odd there wouldn't be a created from if you created from the SO. Oh, I just saw I made a mistake in what I told you. The script should be deployed on the RMA, not the SO!. That should already make a lot more sense :D

easy peasy ma'am - afterSubmit(type){ if(type=='create') { var createdFrom = nlapiGetFieldValue('createdfrom'); var so = nlapiLoadRecord('salesorder',createdFrom); so.setFieldValue('custbody_checkboxfield','T'); nlapiSubmitRecord(so); } } Deploy this on the Sales Order record Replace 'custbody_checkboxfield' with the…

You have a typo - searchresults.getValue('custentity_nosldt') should be searchresult.getValue('custentity_nosldt') i.e. no 's' on searchresult

The basic logic seems sound. I don't see why you calculate a value for jobnumber, it doesn't seem to ever be used. But the only big problem I see is: var setjobnumber=nlapiSetFieldValue('jobnumber', 0); Firstly, nlapiSetFieldValue() does not return anything, but that's not really important. The problem is that you can't do…

It's not a problem, it's a feature ;) Seriously though, what are you trying to do client-side in view mode?

var column= new nlobjSearchColumn('locationquantityonhand', loc) should be var column= new nlobjSearchColumn('locationquantityonhand') there is no join. I think 'equalTo' might have to be 'is'. They might be equivalent, but I always use 'is'.

No. You can't run client script in view mode. You can run beforeLoad script is view mode though, if that helps.

Did you also get rid of loc in your column and getValue ?

Checking the form via "if (nlapiGetFieldValue('customform') != X ) return;" is the way to go. Did you correctly replace X with the internal id of the form?

Well, you can always flip the logic around and do: function beforeLoad(type,form,request) { //only run this script if customform=111 if (nlapiGetFieldValue('customform') == 111) { form.removeButton('emailbutton'); form.removeButton('print'); form.removeButton('createcashsale'); } }

A) !== should be != B) X is not set anywhere. Do you undertsand what is meant by "replace X with the internal id"? Your form has an internalid, like all Netsuite objects. You should be checking something along the lines of nlapiGetFieldValue('customform') != 1234 C) The { following the if statement is superfluous and…

Nope, sorry

I forget - was there functionality released last version that shows you the cost of an Assembly? If not, I know we built a script that does just that. Sums the cost of all members, as well as sales price of all members, and writes it up on the item. Did you mean you were looking for something like that, or you meant you…

Interesting project. I'd probably go with Custom Records tied to the Dealer, with fields like Date, Part and Stock Level. You'd then be able to build a saved search, and maybe just stick in as a sublist on the Dealer, or if you have other ideas, maybe use some suitescript to call searches and get some numbers or something.

The Address tab cannot yet be customized, so no.

Nope, not triggered. Your only option is using recalc().

Basically you read through the 'member' sublist of assemblies, and nlapiLoadRecord each one, recursively drilling down (recursive being a big word, you can do this non-recursively) into each member in the case of Assemblies containing Assemblies. Use some arrays to store what you find, sum it up, display it.

1. 'Create' is invalid - therefore that part of your script will never run. The correct spelling is 'create'. Capitals matter. 2. You cannot and definitely should not (even if you could) affect inventory levels directly. You must go trough an inventory-affecting transactions like a Inventory Adjustment. So your script…