user10648298 Newbie

Us too - we tried in our test accounts and the lastModified behavior is working fine. The next step is to file a case with the SOAP request/response you are getting and we can take a look at it on our side using a copy of your account. -John

Your SOAP's "reference" element has xsi:type "platformCore:reference" - I don't believe you need that. Try <platformCore:reference xmlns:platformCore="urn:core_2_5.platform.webservices.netsuite.com" type="salesOrder" internalId="666"/> What did you use to generate the SOAP and when did you see the change? -John

Sort is not available. Can you store the internalId in your local database as well? If so you can skip forward in the results until you get to the correct page. Alternately you could search by date windows, most of the search time is spent retrieving found records vs figuring out which records to return. Thus with a small…

Try calling getSelectValue() on timebill_caseTaskEvent to get a list of possible IDs and select one from that list. -John

You need to set BodyFieldsOnly to false in the SearchPreferences in the SoapHeader. See the help or the sample applications on how to do this. -John

One user gets both one Browser License and one Web Services license - you can use both at once. So just have each user enter their credentials into the WAP application - no additional licensing. You cannot have more than one user use the same license concurrently. The logins will log each other out or you will get the…

I think this is issue 146642 - please file a case and reference this. Please state what the schedule for the search is. -John

Your best bet for now is to use Axis 1.4 as we know that works. One thing to make sure of is that you have our patched Axis version as it contains a couple of NetSuite specific patches (for example for cookies) How is the sample code failing for you? -John

I don't believe there is a way to disable phone number validation, and pre-validating against NetSuite would be challenging. I think you have to go with the 3rd option and do the validation yourself. One way to do this is to have 3 or 4 phone number fields for area code, prefix, number and extension. -John

mterui, You need to use the .NET "reflection" libraries for this. The .NET libraries will have the type information in the object that is returned. -John

We are testing a 2008.1 version internally, but the 2_6 version should be working properly. Go into the NetSuite application and make sure it shows up in your calendar - Activities->Scheduling->Calendar If the event does show up on your calendar, double click the widget (you should see the fingers touching), then right…

Does it work against 1.3 (the out-of-the-box code)? That fault means it understands your credentials, but thinks they are incorrect. Do you have the code/message for the fault? -John

I think you need to perform two searches in that case. -John

Since these are historical, you could disable "conditonal defaults on add" at the SOAP level. -John

You can do a search for all the items. Collect all of the item internalIds into an array and do an item search by internalId. Now you are down to two calls (one for the transaction, one for the items). Just curious, what do you need the item type on the transaction for? It's not a use case we've heard of often. -John

Are you specifying your account during a SOAP login or are you visiting the endpoint with your browser? -John

You need to update your web reference and point it at the new WSDL location. Read the release notes (when they come out), and look for fields that you use that have changed. That should give you an idea of how much you need to re-code. -John

If you visit http://status.netsuite.com/status.html, you will see we had a transient disruption, and I believe your jobs got caught in that (the timing matches). -John

Did you update your web reference to the 2008_1 endpoint? -John

You want to do a SupportCaseSearch and use the customer join. If your customer's internalId was 23, you would do the following. <search xmlns="urn:messages_2_6.platform.webservices.netsuite.com"> <searchRecord xsi:type="ns2:SupportCaseSearch" xmlns:ns2="urn:support_2_6.lists.webservices.netsuite.com">…

The sample applications are here : http://www.netsuite.com/portal/developers/resources/suitetalk-sample-applications.shtml. This is probably the best place to start. Alternately, to view the documentation, log in to the application and click the "Help" link at the top right of the page. This has our fully searchable,…

Do you get the same error when going against the 2008.1 endpoint. -John

Ironside is correct for a standard user. We have a special user license you can purchase that allows up to 5 concurrent sessions with the same credentials. If you go over 5 concurrently, you will run into the same problem. One solution is to have retry logic if you get the "concurrent operation" problem. In terms of…

How would you do this through your Web Browser? I think you'd be stopped in the same way. You could update the item lowering the minimum quantity, update the sales order, then reupdate the item. -John

"_IsAuthentication faliled" is not a NetSuite error - it must be how your client is interpreting an error. Are you using .NET and do you initialize your CookieContainer as = new CookieContainer(2); If so, just delete the 2 [ new CookieContainer(); ] If not, do you know what the NetSuite error you are receiving is? Is the…

The "no corresponding wsdl:fault binding found" messages should disappear with the 2009.2 WSDL. Please try generating your proxy classes again with 2009.2. Note that you won't be able to use the endpoint until your account is upgraded. -John

We do not remove the Beta tag until the last of our customers is upgraded to 2008.1. However it is worth starting development with 2008_1 now as it's quite stable. I would advise rebuilding your proxy classes once the tag is officially lifted, but what you see now is very close to the final product. -John

You may want to repost in "Best Practices" as this is the Web Services coding forum. https://usergroup.netsuite.com/users/forumdisplay.php?f=56 Good luck, -John

Yes - use the PromotionCode record, specifically PromotionCodeSearch. You can see it in the marketing.xsd and common.xsd (the latter contains PromotionCodeSearchBasic). -John

Is this a multi-threaded app (could another thread in the app be using the session)? Are there reproducible steps (will logging out twice in a row do it?) -John