Weeeell... yes and no. If you've got a script running and strictly looking at the item record, you'll have no evidence that the value change. You won't know. You would need to add a custom field where you would store "previous qty commited", updating that field every time the script runs, and comparing that field to…

Bill:Open = VendBill:A Bill:Paid In Full = VendBill:B Bill Payment:Voided = VendPymt:V Bill Payment:Online Bill Pay Pending Accounting Approval = VendPymt:Z Cash Sale:Unapproved Payment = CashSale:A Cash Sale:Not Deposited = CashSale:B Cash Sale:Deposited = CashSale:C Check:Voided = Check:V Check:Online Bill Pay Pending…

Wow, I just checked on a demo, I don't see any link either. Well then, guess you'll have to run a for() and compare internal ids/qty/amount between the PO and SO to match items :(

If it's just to debug the actual code, you can Save & Execute it so it fires off right away. Otherwise, see this thread

You could, on the schedule page, schedule the script to run every hour. That way, worst case scenario, you get maximum 1 hour of downtime on the script.

The scripting approach definately would use a custom field as per your description. It's really just a script that would assign 1-2-3-4 to lines. Its only "complexity" is dealing with line removals and such.

There are no parentheses around throw. throwExc = function(p_sDescription) { var oExc = nlapiCreateError('-1', p_sDescription); throw oExc; }

I would say custentity_betaclient does not exist in your prod account but does exist in sandbox. Perhaps there is a slight internal name difference.

Hi Olivier, Thanks for your answer. Do you mean Special Order OR Drop Ship? We are using the Drop Ship functionality as the item I am using for testing has the "Drop Ship Item" checked and is therefore not a Special Order. The PO is automatically created from SO approval. Shouldn't the orderline be populated? -Tris Yes,…

It can otherwise be achieved with scripting

There is only a link between PO and SO if you use Special Order of Drop Ship to create the PO from the SO. Otherwise, Netsuite has no idea why it should link the lines.

The closest there is is nlobjRecord.getAllFields(). This will not return the type of field, however. There is currently no method to return the type of field for any record.

Well that sounds more like an error in your script. getCode is usually used on error objects, however it doesn't work on non-Netsuite errors (i.e. pure javascript errors). Try changing your code to err.message instead of err.getCode() for now. EDIT: Oh yeah, I spoke to Netsuite and this should not be occuring. So maybe a…

There are no Time fields in Netsuite, so it's not really an issue. You'll basically be writing into Free Form Text fields which accept pretty much anything.

Is your script a Scheduled script? Sounds like it's a UE script, which cannot be rescheduled (since they are not scheduled in the first place).

Oh certainly, I thought you knew. Mainline is VERY important when performing transaction searches. Basically, if you run a search on a transaction, Netsuite returns 1 result line per line item, some more lines for taxes and shipping if you have that, and also 1 "main line" which represents the "body" of the transaction.…

Try setting it to "SalesOrd:B"

Are you setting your defaults on lineInit, fieldChange or postSourcing?

This is not possible nor is it desireable in a formal ERP system. You'll want to make an Inventory Adjustment transaction to adjust stock.

You can add a button in view mode, and that button can run code. Not sure if you can pop open a SO entry screen with value defined in the fields. I think I'd go with a URL parameter that would act as a trigger for scripted value defaulting on the order.

Hi Carl, We are a Netsuite Partner and Customization is right up our alley. I can provide customer references if you wish. Whatever your scripting needs, we can help.

You forgot to use mainline = T

That's not so much a workaround as the correct way of doing it, so you're all set then.

nlapiFindLineItemValue() does not exist. You probably mean nlapiGetLineItemValue(). Check the Help for the complete API guide.

Ahhh. No, indeed, can't change much of anything in there.

The Make Copy button won't work? Note that you can't have 2 transactions with the same tranid.

durbano If you don't find a local contractual worker, and you want to consider using a Netsuite Partner for your customization needs, please get in touch with me via the coordinates in my signature. Best Regards

Olivier, nlapiFindLineItemValue(type, fldnam, val) was added to SuiteScript recently, at least i can find it in Help section. I have never actually used it. No kidding - thanks for the correction

1. No, you would not be able to add fields to the Build Assembly transaction screen. 2. As above, there are no extra fields to fill in as Assembly time

Is your script deployed to All Roles with no other permission box ticked in?