user10648298 Newbie

I would work with support on this as there is probably a subtlety involved. The warning messages can sometimes be misleading if there is also an error, since once you are in an error state it may trip warnings that don't mean much. -John

Excellent explanation cpforbes. I would just add a couple things: 1. The new PHP Toolkit http://suitesource.netsuite.com/s.nl?it=A&id=39&sc=2&category=262 greatly aids the PHP development process 5. The UI is essentially the Database Schema for your WS applications. Whatever you can do in the UI, you can do in WebServices,…

Sorry to hear this is going badly. I PM'd you with some diagnostic steps. -John

Does this happen all the time? Is it only with this specific custom field or others? -John

This means that the internalId specified does not correspond to a purchaseOrder (it might be a salesOrder). Look in the browser and double check. Also, you seem to using PHP - I suggest taking a look at the new PHP toolkit - http://suitesource.netsuite.com/s.nl/it.A/id.39/.f . This provides much better PHP support. -John

The SOAP is mostly there for informational purposes, you program against NetSuite in Java/.NET/PHP, etc. Each of these languages produces SOAP which you can compare against Svilen's if something isn't working. To create a custom form go to Setup->Customization->Entry Forms (for CRM records) or Transaction Forms (for…

Can you file a case (post the number)? -John

You should see the same fields in your WS results as you see result columns in the browser. -John

There are no good javascript toolkits for SOAP, or at least nothing I could find (I've looked a couple of times). This sounds like a difficult project. My suggestion is to use a trace class in .NET (or turn on logging in Axis/Java) and make the requests you'd like to make. Use those requests as templates. -John

Please file a case with support (and post it), we are looking into it.

Use the login() operation, with their email/password, your company's account id and the customer center role id. This will return isSuccess true or false. -John

Fix 151380 has definitely been released (and your case is appropriately attached). Have you tried recently (and if so when?) -John

We are currently planning to GA the WSDL in early October. However, if you have been upgraded, you can use the new endpoint. Steve Klett, The result columns have some complexity. The same structure serves as the request and result columns. The documentation will be released on this shortly. -John

I would suggest giving your users the Customer Center role in NetSuite. Then you can attempt to log them in via web services, and authenticate them based on success or failure of that proxy login. Storing passwords (any passwords) in cleartext is strongly discouraged. -John

Have you tried it on the NetSuite WSDL? In particular I am curious if it handles abstract types. -John

Issue 151380 will be fixed in tonights release. -John

To amplify, most likely you don't need any applicationId at all. -John

There are some item subtypes that are not supported (and thus not returned) in Web Services. We will have to investigate why the type filter is not working for you. -John

Can you restart your integration application? I believe it will be fixed after that. -John

What message are you getting? Is the search too slow or are you getting a timeout message? -John

I believe you can get around this by increasing your timeout - how long is your timeout. -John

Create a file "client-config.wsdd" in your working directory. The contents should be as follows <!-- Save this file as "client-config.wsdd" in the working directory of your Axis client. Axis will load it automatically. The configuration here tells Axis to save all incoming and outgoing XML into a file named "axis.log"…

It's 1 roundtrip instead of 2, and it will save you the amount of time the login operation took (after the first operation). -John

In that case you won't see a performance improvement. The one advantage is that we detect the "stale or non-existent" sessions for you. Many users simply login before each request, they would see the improvement mentioned above. -John

Was this on Beta or Production? Also, you may want to look at the new PHP toolkit as it takes care of a lot of these problems (including using the new Request Level Credentials feature that eliminates the need for login or session management completely). -John

It's not possible to do so - the record type must be in the WSDL for it to be returned. -John

Yes - https://webservices.beta.netsuite.com/wsdl/v2008_2_0/netsuite.wsdl Note the new version and the "webservices" subdomain. Make sure your account is live on Beta (login via the browser) first. -John

the "customer" object you submit does not get updated to have the new internalId. Instead you get a "WriteResponse" from the WS call that encapsulates a "RecordRef" with the new internalId. I totally missed that looking at your code. The SOAP should look like the entityStatus tag in your customer add soap. -John

This looks like a bug in the .NET compiler. If you have another computer, can you install visual c# express on it (free) and see if you get the same compiler error. You can also try deleting and re-adding the web reference. -John If so, I think you need to file a bug with Microsoft. Here is a blog on it -…

Do you have multiple currencies on? If not, you don't have to set the currency.internalId -John