I have a similar situation in where I want to restrict shipping methods based on items added to the cart. I checked into the RemoveSelectOption() and it's only useable on scripted UI fields. It isn't able to be used on standard NetSuite UI fields (at least from what the documentation stated).

Yeah, I saw it working fine beginngin yesterday morning. Sometime must have gone on over the weekend I'm guessing that got cleaned up by the beginning of the week.

I'm having the same issue. The parameters passed to the fieldChanged and postSourcing functions are (type, name) and mine are not working. I keep getting the JS_EXCEPTION TypeError Object Expected like you are getting. Is there is issue with NetSuite currently? I've never run into this problem before writing Client…

Are you able to attach a function to a button as mentioned above? I have tried this to no available without doing something like calling a Suitelet. Example: form.addButton('custpage_test', 'Test', 'testFunction()') function testFunction(){ alert('Test Worked!') } This does nothing except return an object not found error.

I was just including the function below the function that created the button which did not work. I managed to get it working by creating a string which included the contents of that function and putting that for the script parameter. Not sure if that is the best way to accomplish it, but it worked for the View event.

I have the same problem and I'm using IE8. My JavaScript files are being uploaded as either HTML or XML which doesn't allow them to be used as scripts.

For "Mine", you can also use: filters[0] = new nlobjSearchFilter("salesrep",null,"is",nlapiGetUser());

You could search for the alternate contact for the customer by doing a contact search and use a filter for Contact Role = Alternate Contact and Customer = Customer ID from transaction. It'd be a little different than above but not too much.

Both RedMap and Bill.com do this - you can check out their integrations in the SuiteApp listing. There might be some others out there as well - but those are the big two that come to mind.

We have to do this fairly often when vendors ship drop ships to our warehouse vs. directly to the customer by mistake. We handle it by receiving the purchase order (Transactions > Purchases/Vendors > Receive Orders and using the Receive link). We then fulfill the order as normal. The integrated shipping still works from…

You can set the postingperiod field by using nlapiSetFieldText and format the posting period accordingly based off the date/logic (ex. 'Jan 2012')

We have the same issue which started a few days ago. It doesn't happen on every single order/transaction which is strange. I guess we'll just have to make it through for 2 weeks somehow.

You could write a small script that auto-checks the box on the Message before being sent out. You'd just have to remember to uncheck the box if you're just sending normal correspondance.

the field id is "expensedate". a little tricky to find but if you hover over the date picker button it shows it in the status bar.

You would do a scheduled SuiteScript based off a transaction search. Most likely x-number of days past when an order has shipped. Then you would just pull the information about the items from the sales order into the script in a HTML format along with template/marketing information you'd like to include in your email. Get…

All our users have access to this folder as all of our users have access to the records we save them on. I haven't tried saving something to a record that is more restricted, Employee record, for example to see how the permissions flow back and forth. You'd have to check with Box on that one. So far, we use it for…

Yes, Box preview is very good although some times can be a little quirky on some file types like TIFF files but almost all others are very straightforward. Searching is very nice too as they have full text indexing on documents so it will search document contents too - not always a blessing though

We use Box as a whole as a replacement of our file server. We're not 100% there yet, but we're well on our way. Since we're big NetSuite users, the integration with NetSuite has been great. One of the main uses we have is to link supporting documentation to transactions - quotes we get in from our vendors linked to an…

Yes, we've been using it for almost 4 months now. I'd be happy to share experiences and answer any questions.

Yeah, we editted their integration to work around this and use the transaction number vs. the internal ID.

With the Box integration, you should be able to drag/drop directly into the Box subtab on the records or the one that is full page on the Box main tab.

Go to Home > Set Preferences > Transactions and uncheck the Inventory Level Warnings checkbox.

Are you referring to all for the same line item? You can generate multiple PO's on a single SO to different vendor for different line items; however, you can only have a single PO per line item natively.

You can use a script/workflow that forces the status back after submission of the order. When loading, you store the previous status in a hidden field then set back. However, this is very tricky as nearly every time a related transaction is created/saved it can change the status - for example, when the order is billed.…

There are some examples and fairly good documentation within the NetSuite help documentation.

Are the quotes marked to Email out (checked under the Messages tab)? This might be causing the issue when the Mass Update runs.

You can create a scheduled script that is set to run nightly. In your script, you can run a saved search that looks for all quotes that have the Expired field date matching the current date. Iterate through the search results and update the status/probability fields to mark the quote closed. I haven't checked, but you…

The field you'll want to set is called 'entitystatus' I believe

Did you try using the full URL?

Is this a variable priced item? If so, you can pass the price in with the add to cart URL call.