We merge, but it has got to be confusing for our customers.

Just heard from NetSuite - Enhancement 41382: - Ability to restrict shipping items offered online by the shipping address looks like it might be going live in 2009.2. Awesome.

I understand but the more important and germane part is that we do not offer ground shipping to those locations, hence why we're looking for some means of limiting the choices on the web checkout.

Any eta for this enhancement?

I am not seeing the link to this? Do I have to be logged in?

I'm going to perform a bit of thread necromancy here. Holding the Necrosuitecon, chanting in leetspeak, all of that. We need these enhancements. Both 76328, and 30643, which is the logical corollary the ability to see IP addresses of our web visitors, specifically our online customers. Other packages far outstrip what…

dj (or other NetSuite employee?), do you know if there is anything happening on this enhancement & its pair? Thanks!

Please vote for issue 46431 to help us prioritize this enhancement higher. Has there been any movement on this enhancement? This is a nice way to increase customer trust. Its been open for some time now with 70+ votes. (Also, the support rep on the phone has NO idea what I'm talking about. They thought it was a request for…

I think this is something we'd be interested in as well.

You need to add: contactRef.typeSpecified = true; EETS ALIVE!! That was it. :D I would have never thought of that though. Thanks.

So I found a solution (yay search) but I am confused on HOW it works. ((RecordRef)response.baseRef).internalId; Its my understanding that this takes the baseRef of the response (which I can see in the SOAP response) and casts this to a RecordRef? Is that correct?

Okay, getting somewhere; I changed tacks and went with a solution from this thread which was to simply assign contact.customer to the customer reference that I had just created. Which works somewhat but does not assign the contact to a role. We'd like primary role to be set, so that's next.

Geh, still getting nowhere. This is what I have so far, am I even going the right direction? protected Status Create_Customer(NetSuiteService service, String companyName, String email, String unsubscribe, String phone, String firstname, String lastname) { // Create the new customer Customer customer = new Customer(); //…

Okay I think I see how it works in the SOAP, but now how to make it work in ASP.NET? To me, it looks like that is what the example in post #3 is doing with the AttachContactReference object. I'll have to take a look at the SOAP, I guess. Thanks for the feedback, I'll keep hammering on it.

Nevermind - I misread this.

Well, fine if NetSuite is just going to be stupid, then I'll get stupid; to_date(substr(to_char({systemnotes.newvalue}),1,instr(to_char({systemnotes.newvalue}),' ')-1)) returns what I need. Haaaaaaaacky but it'll work.

Yeah it just returns Error An unexpected error has occurred. Please click here to notify support and provide your contact information.

Portland thread necromancy! Rise up! I am trying to do something similar - I want to test the original value of a date field on phone calls. I can get the text without issue of the original value via system notes, but when I try to_date, I either get an unexpected error or Error: Invalid Expression. The text that I'm…

Hey Corey; What I really need to do is strip the time & timezone out, everything is going to be the same time zone (it's a date field being set via nlapiDatetoString in script), so that I can test the formula as a date for "within this week". Something like this - but this doesn't work either;…

Thanks - I assume by location you actually mean a different NS location, and not just another bin? You can't declare a bin as un-fulfill-able from, right?

True, but that still doesn't stop the picking ticket from printing a blank bin, does it?

The goal is to find a way to prevent inventory on the dock from being made available for fulfillment because we don't fulfill from the dock. If that makes sense.

Just had a web order error out with "Could not calculate cost for the selected Realtime rate. The UPS Online Realtime Rates System is temporarily unavailable. Please resubmit your rate request in a few minutes." Happened during an afterSubmit script but the script isn't doing anything explicit with rates.

We've seen a few issues as well - I filed a case with support (case #1363018) but haven't really been able to reproduce the issue.

We've been having the same problems - NS has said that it's due to Drag & Drop Functionality. However, we've had affected users turn it off and still no effect. We received this from NS; As per our Quality Team, the performance issues have been addressed in the latest version of the Drag and Drop Bundle (41309). Kindly…

We've noticed this too - especially annoying as we have migrated away from NS ecommerce and so login access is meaningless. I suppose its time for a Mass Update.

We too are having incredibly slow responses on Transactions, especially on the Approve SO -> Create Drop Ship flow, and creating Item Fulfillments. We have a few SuiteScripts in the process, but so far, haven't identified any issue. NS has created a defect for us that we're trying to get pushed to an S1 as we are getting…

Case #1447385 I've encountered issues where you get an error when trying to assign fields a field group, "This custom field already exists." No response from support as to if this is a defect or not (in fact, Wilma found a workaround and said, "Welp, case closed!") Only work around I've found is to remove ALL field groups…

We have this too - how did this go long before it got reported as a defect? Anyway, this is what I saw; Defect #- 196821: Shipping Item "Display Name" is displaying internally instead of the Shipping "Ship Name". SUMMARY: Defect 196821: Shipping items showing display name WORKAROUND: None. Your defect has been prioritized…

Sean, Any word on when this will be fixed?