Printing a custom record would normally be handled through the usage of the nlapiXMLtoPDF() suitescript API, which allows you to custom print anything.

nlapiGetNewRecord() returns a read-only object, so that won't work. Since you're in beforeSubmit, you would not need to load the current record anyway. However, NS does not refresh objects dynamically, so by submitting your invoice, the current Payment record would not reflect the change. So attempting to act on that…

Can you post your code snippet?

You'll want to use a beforeSubmit script, with verifications on old record vs new record, or maybe to make things simpler just check if the current entity is already a customer or not. If yhou detect you need to make him a customer, just load the customer and set his status to closed-won or any other status that means he's…

That's a very important point for playing with permission, actually. Whenever you change someone's permission, before testing, that person (or you, if testing in their place) should log out of Netsuite and clear their cache. Otherwise it is indeed true menus do not refresh properly.

Did you limit reports in his Role?

Oh oops, sorry. You want nlapiSetCurrentLineItemMatrixValue()

Ah you can't use DOM to set the value of things in Netsuite. In the case of pricing there is an API just for that, nlapiSetMatrixValue(). It's a little tricky to use so check the help, but that's how you set prices.

Hi At the footer of your Income Statement, set the "Column" dropdown to "Department (Hierarchy)"

It's still not possible in most reports. Short of throwing it to Excel and doing it there, or perhaps building some sort of formula-based saved search with the rollup built into it, it can't be done. Note that I haven't played much with the new custom segmentation options. Maybe these offer rollup capability?

What is wrong with that? Using the footer Department Hierarchy allows to see numbers rolled up at the Parent level, the parent alone, and then each department alone. Is that not what you were looking for?

Hi Sam, This is a common setup as many Netsuite customers sell products on a s ubscription basis. We have coded versions of what you describe above several times (everyone always has slightly different needs). You have pretty well identified the components - some UE scripting on the sales record, a Custom record to monitor…

Think you'll need to customize a report then. Department reporting is not like One World subsidiary reporting, there is no consolidated view at the parent level.

Are all your orders entered manually? If you use Client-side to handle core logic, it won't run if orders are created via CSV, Web Services or by batch processes. Client-script should generally only be used to control UI behaviour.

Oh cool, didn't know mass update scripts could delete. See, always learning new things :)

I do not believe Mass Update scripts allow deletions

Hmm, shouldn't be too hard. While it's possible to update the field on the item real-time when a PO is saved, there are too many angles to take into consideration (create, edit, delete, etc). I would recommend a nightly scheduled script instead. Data will be slithly less fresh but I don't think that's a big deal. The…

Mhm, agreed. Wish there was something I could to to help :(

Can they squeeze it into a weekend or something?

We have several customers on them. Performance is certainly "better" but it's hard to quantity. What is causing you to consider this? Slow saved searches?

Yes, using suitescript

Right. The backend architecture is always transparent to end users

Yes, there is no difference to using/logging in a dedicated server to what you're doing now. In general, yes, Dedicated Server should help the speed of all of these things. I would say the next step is to talk to your Netsuite Account Rep. He should ask you for a bunch of information about your transaction and usage…

Nowhere, that is not possible. Address section cannot yet be customized.

"oldRecord.nlapiGetFieldValue" should be "oldRecord.getFieldValue" Try that and see if there are any other problems

nlapiGetRecordType() and nlapiGetRecordId() should be sufficient

The process to add a button in view mode is considerably more complicated. You need a first User event script with beforeLoad to add the button using form.addButton. In the form.addButton you need to specify the function name to call. This function must exist in a client script. The client script must be dynamically…

There are several URL that should allow users to reach your web store, but they should all have exactly the same experience. If you are seeing differently I suggest you contact Netsuite Support.

Yeah, just call a nlapiLoadRecord or nlapiSearchRecord or nlapiLookupField to access the info. It's weird cause you're ON the record, but in reality, you're not. So just access it as it it was a foreign record.

On each Customer record, under Info, you will find an Email Preference dropdown specifying how you want to send it. Further, under Home->Set Preferences->Transaction, each user can specify his own default.