Have you considered the "Ship Date" field on the Sales Order? Couple that with the "Do Not Allocate" option and you might get what you need.

We have this exact same situation. While not perfect, we handle it with a saved transaction search, and email alert type = receipt item qty available - qty received < 0 The second criteria line tells me that the item received was committed to an open order (and not to stock). The email alert is sent and the recipient…

You could script it -- or set up a saved search to alert someone once it happens -- or you can check 'Default Items to Zero Received/Fulfilled' in your accounting preferences.

If you have the sales rep on the sales order or on the customer record, you can access those thru joined criteria Created From Fields... Sales Rep Customer Fields... Sales Rep

Make a saved search,with criteria type = fulfillment sales rep = [his name] results Number Name etc and have it email him on the {results} More generally, you could set up this saved search to email *any* sales rep, by emailing the sales rep based on 'Recipient from Results' fields.

Thanks Brett, that's very helpful. If I'm understanding your code, the body of the email is generated in the script, which will accomplish the immediate goal of getting the tracking numbers in an email. I'm going to chop up the script and get it implemented! Long term, I am hoping to do get the tracking numbers in the…

OK makes sense now, I once read that regular expressions can only be understood by their author. My fedex tracking number was 15 digits, apparently fedex ground uses 3 extra characters than express, so I'll just add a condition for length of 12 or 15. Thanks Brett for your help!…

Very nice code, thanks! I got it implemented and I simply append the tracking numbers to the email, so it's working with the template. One problem I had with the script was that it didn't recognize my fedex numbers, so the makeTrackingLink function was returning nothing. I modified it to return plain text if it couldn't…

I looked into this kind of automation too, we have fulfillment labels and packing slips to print, and there are lots of clicks. If you are using IE, you can use activex to automate some/all of the steps. FWIW, I chose not to do it because I don't know activex and I dont like IE security opened up.

This happened to me a while back. In my case it's from a bundle script that modifies the record aftersubmit, so I get an email before the script and one after. Maybe this is happening to you too?

Check out M Files they have a nice system integrated with NetSuite. Also you could make your own with a hosted system or with Google Docs.

Good insight Brian, thank you. For #3, the best advice is never use Internet Explorer. I switched all 30 users to Chrome three years ago and have had 0 malware since. I also have 5 users on chromebooks where malware installs are nearly impossible.

Yeah I agree, I have one IT consultant who says that password should have >1 CAP, >1 lowercase, >8 characters, >1 special symbol, and >1 number. Oh, and change it every month. wtf, no one can remember that so it's completely vulnerable to the post-it-note hack. Yesterday I had to change a password for one of my netsuite…

This is a really nice bundle, it's well built and easy to use.

Sounds like a cache problem

rrennie - we experienced this too, for customers without any transactions. It turns out there was a Contact associated with the customer, and they had different subsidiaries. That was the Parent/Child that error, so it was a little misleading. I found about 50 cases, I think that these were all web-created contacts, and…

Thanks Frederic. I tried that and it still has the same problem, only 1 line is on the sublist and it's not committed. I also tried true in the firefieldchange and it doesn't work. Time to open a case with support!

For me it was easy to clean up with a CSV import, I just had to reassign the subsidiary of the contact. But.... it's an ongoing problem, and I have to scheduled time every week to clean up contacts.

The synchronous parameter worked... I've never had to use that before, thanks for your help!

What kind of item record did you test with? I'm using a lot numbered inventory item.

Before I contact support, can you take a look at this and tell me if there's something wrong??? I've tried all the crazy combinations of Insert, Select, etc but commit never works, I end up with only the last bin (312) on the sublist, and the line is not committed. If I reverse the code (switch 194 and 312) I only get bin…

Did this ever ger resolved? I'm having the same problem with nlapiCommitLineItem('binnumber') on an item record.

SPS should be able to handle this as a change, rather than a create. Your customer's order should have some unique identifiers can be evaluated. I would showing SPS an example and they should be able to work with it.

The customer name is probably a component of the opportunity name, hence it shows in global search. There is a trick to make any standard field be global search searchable: create a custom field, check the 'global search' box, then write a very simple script that sources the custom field from the standard field.

This extension is so helpful, especially useful when I have complex searches with formulas or joined tables. Big thanks to david.smith !

This could be done with scripting or possibly workflow.

I don't think you need the semicolons. Also is {itemid} always long enough? You should perform a length check.

Alternately, you could create a custom 'Transaction Column' field for Estimates and Sales Orders. Source this field from the Item Description, set it's 'Display Type' to 'Disabled'. Next, on your Estimate and Sales Order forms, hide the native 'Description' field and show this field instead.

You could definitely script this with setMandatory(mandatory), setting the field to mandatory on create. I believe this would require a beforeLoad script. You could also run a beforesubmit script or maybe even a workflow that wont allow submission if type = create and email is null.

yw schick, my thought is that the script should run on intervals so that you don't have to consider multiple executions in queue, and you don't have to consider which item(s) belong to which receipts/executions. And this should resolve any ambiguity of when the items get committed. Also, the checkbox technique is a little…