Olivier Gagnon NC Red Ribbon

There is no way to implement OR logic using the field config screen. You can do it with some scripting though.

I imagine this is certainly doable. A quick google search found some scripts that do this. You'd just have to plug them in and complete with a quick nlapiSetFieldValue().

addField() returns an reference to you field. e.g. var field1 = form.addField(...) So later all you have to do is field1.setManadatory(true)

record.getFieldValue('source') will return something like "Web (yoursitename)"

User Event scripts are not triggered by Web Store navigation. You can only have client-side javascript (and we're talking javascript without Netsuite APIs here) written into the the web store pages (such as on templates, etc). So you will have to reconsider your approach.

You can call a Suitelet, that's one way.

Have you logged a case with Support?

This may be related

Yeah someone posted not too long ago that the link between PO lines and SO lines was gone apparently. So, that means you'll need to iterate through the lines in both records and match by item internal id. This should be sufficient if you never have the same SKU on 2 different lines, otherwise you can match on internal id +…

Hi You cannot remove the items or you'll lose the link. You'll have to keep them and edit them, rather than removing them and re-adding them.

Oddly enough there is no field that specifically shows this. However, you can easily calculate it with quantity - quantityshipped. If you use pick-pack-ship I believe that becomes quantity-quantitypicked.

tranid does not require a join, you're getting info from the current record. I'm not 100% sure name is a correct item field. Might be itemid or something.

Woah. That's going to be pretty hard. If it was something else than a PDF - like having a Suitelet that guides the user through the color selection and purchasing process - it would already be a handful. A PDF to your current browser session is going to be pretty rough.

Change it to parseFloat(current_line_qty) > parseFloat(current_line_onhand) Javascript compares things as strings by default. So 9 > 10 would return true because 9 is greater than 1.

This might be related to a change I was made aware of recently. Instead of using nlapiSetLineItemValue(), try using sublist.setLineItemValue(). Apparently using nlapiSet... is no longer supported on Suitelets.

Hi Nathan, Please refer to the documentation for record.setMatrixValue(group, fldnam, column, value) Cheers

Ok, but it was working before, and now it's not. Those kind of things are expensive to fix :( Thanks

It behaves like a regular field, i.e. nlapiGetFieldValue(your_field_name)

Ah ha, then yeah, you need to create it with scripting. Then to answer your original question 1. Go to Home->Set Preferences and turn on "Show Internal Id" 2. Go under Setup->Customization->Entry Forms, find the form you use, and the ID will be written next to it.

Oh. record.getFieldValue('customform')

Do you really need to use beforeLoad or can you just created a custom field (Setup->Customization->CRM Field) and use that? They are much simpler to work with since you just configure them rather than code them.

beforeLoad scripts do not allow the defaulting of fields, except for Do Not Store value fields, and nlobj custom-scripted fields. You'll want to use a Client-side script instead. Also, your field names are incorrect. Refer to the Help under SuiteFlex (Customization, Scripting, and Web Services) : SuiteScript : Getting…

There is no way to run Client script as Admin. As Brett suggests, you can call a Suitelet, you can call a Scheduled script, or you can move your script to AfterSubmit on your custom record (the button you have now could simply tick in a box, and in AfterSubmit, if that box is ticked in, you run the deletion code then…

Have you tried nlapiLoadRecord()/nlapiSubmitRecord() rather than submitField? A lot of fields cannot be submitted directly.

Hmm, don't know then. I'd open a Case, and in the meantime run a few tests with different senders/recipients to see if you can get it to work at all.

Try doing this - var item_name = oneitem.getFieldValue('internalid');

id = nlapiSubmitRecord(record, true); id is you record internal id

For the sender, you are using the internal id of an employee? Are you doing this from a production account, or a sandbox?

You'll want to use nlapiSearchRecord() to fire off a search and get the minimum price for each item. Doing this one-by-one as items are entered will result in a seperate nlapiSearchRecord() call which will take a few seconds each time. If you have very short POs this might be ok, but if you have many lines this will be…

fieldChange is going to be called A LOT on page init, since it's called even when fields are being initialising. That you see too many alerts is normal - we want to make sure you are not seeing not enough. So, ignoring all the alerts we don't care about, if you change the value call type, what alerts come up?