You could use some JS running during checkout to hide the DOM elements. Grab a nice tool like Firebug, figure out which elements need to be hidden, and write the JS accordingly.

Customize the form in which you want to remove the buttons. Under the Actions tab, uncheck Show from Invoice and Cash Sale. This will remove those buttons from that particular form.

Like Javier said, you'll want to research nlapiXMLToPDF which uses the BFO library to create a custom PDF document which a wide variety of flexibility and options. You can use SuiteScript to extract all the data necessary from the custom record and stage it in the formatted document to generate a PDF.

Had to do the same to get mine to function initially - it was previously setup w/ just Customer Center role and then switched to all roles. I did wait some time in between tries - could also be a caching issue - difficult to tell.

Brett, Been toying with this a bit today. I finally managed to get a recalc event to trigger. Deployed both record-level and form-level (need to test then to verify both work) but deployed script to all roles and released included parameters type and action in recalc function function customRecalc(type,action) {…

your custom field on the transaction should be prefixed with custbody_<custom field name> or custcol_<custom field name> since its a custom transaction body field also, i believe you're only allow single quotes in the SQL statement

I'm right there with ya - I'd love to hear of somebody who's gotten this to work. Even something as simple as showing an alert to the user using scriptable checkout in a variety of events I've not gotten to work. Tried using both form-level and global-level client suitescripts.

I did use nlapiLogExecution to log the error. Something simple like nlapiLogExecution("error", "Debug", "Script is running...") I think placement of the statement may be key. I believe I encountered an error too if I placed this outside of the if statement to check type and action. Started logging lots of times - probably…

You'll want to use nlapiTransformRecord on the purchase order. You can get the purchase order internal ID by using getFieldValue("createdfrom") on the item receipt record. nlapiTransformRecord('purchaseorder',purchaseOrderID,'vendorbill') will return a new record object of a vendor bill. By default, I believe the bill will…

var fulfillment = nlapiLoadRecord("itemfulfillment", ID, {recordmode: "dynamic"}) fulfillment.setFieldValue("shipstatus", "C") nlapiSubmitRecord(fulfillment, true)

Thanks. I was working off an old file so that was why it wasn't working. I initially tried to do this using nlapiSubmitField to change the shipstatus which was not posting to GL impacts, causing the Shipped fulfillment do not be billable.

I ran into the same thing just a little while ago. The only reason I can see for splitting them would be to give us extended access to serial number records, but as far as I can tell that is not the case. This just created a good bit of additional work each time I need to do an import of items (esp. price updates to…

I just confirmed with NetSuite support that you will need to import serialized and non-serialized items separately from now on. You can use the Costing Method field to determine what is serialized vs. not when doing a saved search.

Yes, I'm unable to get into the main websites for production and sandbox. I was successful in getting into the system2 domain. Might want to try that if you need to get in.

Is anybody else experiencing these issues again today? As of just a couple of minutes ago?

We're getting a bunch of unexpected errors all over the place too. I got once right when I logged in.

I had a similar issue late last night maybe 30-45 minutes before you post - just all of a sudden stopped working. Glad to see it seemed to be an NS issue and not my code :)

You could try a summary filter for #1, assuming you're not restricting to main line only Formula Number, Summary = Sum CASE WHEN {custcol_job_isjob}='Yes' THEN 1 ELSE 0 END Use criteria is >= 9

Yes, ours is very slow (east coast here). It seems to have started just recently.

You wouldn't be able to access line item detail via a workflow - you'd have to use a script. You could write a script that either iterated through the line item using the column quantityfulfilled or use a saved search and sum the column and grab the value.

You do could it a couple of ways depending on how your items are setup. If all of your matrix parents are top level in the hierarchy, you could check the field Subitem Of (internalid: parent) to see if its empty. If it is, then you can assume it's a matrix parent. Alternatively, you could run a search for the internal ID…

Are there any scripts or workflows running in the background on your order when they are approved?

Have you tried using 'shippingamount' for the field ID?

We're down as well...need a fix ASAP

How long have you been using website categories in SuiteScript? I've always thought they were unsupported at the current stage of the platform. Can you access all of the fields?

When referring to leave until the next day, have you experienced issues with incorrect values on regular inventory adjustments (not using the worksheet). We use IAs to add cost to products we sell (only ever 1 of a given item). If we do two inventory adjustments on the same day, for example, adj. out at old cost and then…

You should be able to use the transform for this. When looking at the record types, the first column is the type of the record you are transforming so you'd be looking for invoice not customer payment. Either way will work though. nlapiTransformRecord('invoice',recordid,'customerpayment'); OR…

Looks good. You can actually use the nlapiTransformRecord API to create a customer payment from an invoice. This should default your customer at minimum and might auto-apply to the invoice transformed from.

You have to enable Server SuiteScript for your CSV imports to have user event scripts trigger on CSV imports. Note, this may slow the import process. Setup > Import/Export > CSV Import Preferences

your nlapiLoadRecord command should read nlapiLoadRecord('invoice', record_id) It's complaining about the amazoninvoice text in that call