A lot would depend on the format of the CSV, but it is possible to write some SuiteScript code to consume and parse the data in the CSV file to create/update transactions in NetSuite. One thing to check first would be the size of the CSV file. Most of the API file utilities are capped at 5MB.

Hi Amit, I'm trying to do this off of a transaction (PO emailed to vendor in this case). I email the PO to the vendor (using my own email as test). When I reply back, it logs the email under the messages tab but no trigger for the UE script. Does it only work for incoming messages on Cases?

Thanks. Anything WorkFlow Manager can handle? I've heard someone say they've heard that you can create records off of incoming emails from vendors/customers in WorkFlow, is this true?

You can use the 'view' event for a user event script to update the record/refresh data. Simply run your searches, get your values, and update the fields.

I do not think you can change the status of the transaction via nlapiSubmitField as that only updates a single body field. You would need to load the record, set the status field to the desired status (using the transaction enumerated values), and save the transaction. var record = nlapiLoadRecord("salesorder", recID)…

The error looks to be the script looking for an 'AddItem' variable or function that does not exist. Is your script setup correctly with the correct function name (should be addDiscountLineItem) or is there a call in your script to a function called AddItem?

nlapiGetNewRecord() returns a read-only copy of the record. If you want to make changes to the record and submit them, you will need to use nlapiLoadRecord(). Also, I do not think you will need to use both nlapiInsertLineItem and nlapiSelectNewLineItem.

You can call your suitelet with the parameter dependent=yes and then in your return script write back client suitescript something like window.operner.nlapiSetFieldValue(................); Alternatively, you can do like the link above mentions and execute your suitelet and return selected data back to the client using…

You'd want to call nlapiResolveURL for to build your URL from the Suitelet script and deployment IDs and then place that URL into the nlapiRequestURL with any additional parameters if necessary. However, I'm not 100% if that'll give you and work like you need, most unsure if it'll open the suitelet and if so, if it opens…

You need to be sure of two items: 1. In your window.open() call in your before load script, be sure to add the parameter dependent=yes in which the other window parameters 2. When calling window.open in your client script, you actual write this out back to the calling function something like the following var script =…

Make sure you are using a User Event script. Page Init, Save Record, Validate Line, etc. are all Client script functions.

I've seen the issue in Production, Development, and Sandbox accounts.

In further testing, the emails are being sent and coming through to the desired recipients. They are just not being logged under the Messages tab even when using the records['entity']=Internal ID parameter.

To set the price level to Custom, you'd use the following syntax recCustomer.setLineItemValue('itempricing', 'level', 1, -1) -1 being the Internal ID of the Custom pricing level.

You can create the body of your email manually in the script and pass that into the body parameter of nlapiSendEmail. Basically, write a block of code that goes through the line items on the fulfillment record (or gets data back from a saved search) and formats accordingly. The body can include HTML code so you could…

Thanks Olivier that works well.

Most likely KOTNUtil is a library function or function defined elsewhere in the script file.

Aha, Got it working using the string function (issue was with single vs. double quotes and using semi-colons). The only issue I'm having now is I'm trying to run a nlapiSetRedirectURL at the end to refresh the current record which it is not doing. I can manually refresh and see the fields updated so the rest is working.

I should also note that the button is being added to a sales order form, not a custom form built via a Suitelet

Hi Samanthara, The above script is a user event script that only trigger in View mode so I believe the last option will not work as it is a client-side script only and would not be loaded upon viewing the record. Will the library script work for the user event script? Nothing is executing client-side here. I just need a…

This does not seem to be the case. If using inline, I always get scriptlet.nl as the file name and wanting to save as scriptlet.pdf when clicking save. It seems whatever name provided to NetSuite n the setContentType is ignored if using inline disposition.

What about just passing the SO internal ID and writing a beforeLoad script on the customer deposit record to pull in the entityID and memo using nlapiLookupField()?

Yes, wrong field sorry. It appears there is a field called flag called "voided" that needs to be set, but doesn't look to be accessible. May be easier to use Workflow Manager depending on your specific requirements.

You should be able to set the Estimate to status "V" which should change it to voided.

The nlapiXMLToPDF function returns an nlobjFile object which can be uploaded to the file cabinet. Try something like the code below: var file = nlapiXMLToPDF(myXML) file.setName("myFile.pdf") file.setFolder(internalIDOfFolder) nlapiSubmitFile(file)

Name field internal id is "itemid" not name That plus the removal of the join for the tranid column should fix you up

Some information in the fields contain special characters like & that would generate an XML error

Hash functions cannot be decoded/decrypted as you say as they are one way functions. They can only be brute forced to try and decipher. SHA1 can use initialization vectors which can vary between algorithm implementations which may give the variance between the two hash values.

How will line breaks be handled then in the CDATA as it will not interpret them? This would cause an address or line break in say item description to not be recognized.

In this particular script, all line breaks are converted to HTML markup (i.e. <br/>). I tried using it with the HTML <br/> tags and without and still no line breaks.