My Stuff
Comments
-
ExternalId is a peer to internalId and was released in the 2.0 endpoint. It can be used in RecordRefs the exact same way. It is a unique, though mutable, key across the record type. Putting your SKUs in the externalId field is a perfect example of how to use them. You can set the ExternalId in WebServices during an add or…
-
I think Elham means the 1.3 endpoint. -John
-
You shouldn't have to use a delimiter (in fact you can't). Instead you should be submitting a list of the references (one ListOrRecordRef per Multiselect entry). -John
-
If you can put up with a lack of interactivity, you may want to try using async from your webpage. If you are just recording transactions in NetSuite for billing/fulfillment/etc. If you are querying for items, or need the response from NetSuite to continue, then it will not. If you are doing lots and lots of…
-
They are in submitted order. If you submit 10 records and the 3rd response in the responseList is an error, the 3rd record submitted is the one with the problem. -John
-
Thanks Jan. Connection pooling is the highly preferred method of doing this. Failing that you can have each worker thread login when it starts up. We'll handle the pooling on our side. Again, you can not login once and hand the same Session to every thread. -John
-
marcello's advice was correct. You are having a completely different problem (see other thread). -John
-
Can you post the SOAP this is generating? Your code looks correct, though you don't need the ItemSearch, you can perform a search on a the ItemSearchBasic object. -John
-
Do you have custom code on the customForm you are specifying (or the default customForm) that is updating the dateCreated field? -John
-
Glad to hear it's resolved. A way to get both the UI and WebServices behavior you desire is to have 2 customForms - one for UI users with the fields disabled, and one for WebServices without the field disabled. -John
-
Use Axis to generate the proxy classes for you via "WSDL2Java" which is documented by the Apache team http://ws.apache.org/axis/java/user-guide.html This will generate classes such as "com.netledger.dto.v2_5.lists.relationships.Customer" . These are the NetSuite classes you need to import. -John
-
Things should look similar to the way they looked in version 2.0. Can you be more specific? -John
-
One quick thing, has an underlying form changed? Open up a new customRecord with the WS user who is getting the error and see if you can set the custrecord_expiration_date field. -John
-
Inventory Adjustments are transactions, not items. Think of it like a salesOrder, but instead of price/amount there is "adjustQtyBy" on the "InventoryAdjustmentInventory" list. Try doing what you want via the UI, and just translate that field for field into WebServices. -John
-
The longer running a request you have, the more likely something will go wrong. I suggest using a smaller page size - there is no efficiency gained using a page size of 1000 vs 50 if you have to paginate anyway. Also if you do not need the List data, make sure you are using bodyFieldsOnly=True, this gives much better…
-
Are you getting a response from the Web Services operation itself? Specifically, if you add a SalesOrder, are you getting back an nKey or a Fault/Error or a socket error like a connection timeout or reset? It would be really helpful to see the response SOAP. -John
-
We currently do not support multiple users on one session and/or set of credentials. If you need multiple concurrent use you need to have multiple users. There is an enhancement request outstanding to allow concurrent use of a single credential. -John
-
File a case - this sounds like a problem with that specific record. Make sure to include the SOAP, it should be pretty easy to track down.
-
Good news, it will be available in the 2008_1 endpoint which is rolling out very shortly. -John
-
It's not supported yet - please file an enhancement along the lines of "add job field to salesOrderItem schema". This will probably happen when we expose jobs in WebServices. -John
-
Are you getting your salesOrders via Search()? If so, if you set BodyFieldsOnly == true (the default) you will not get back the items. However, you can take the internalId and perform a Get(), or you can search with BodyFieldsOnly == false -John
-
You can use the production WSDL to start writing your code against, even if you haven't been upgraded. Since the last upgrade phase is 10/20, 2.5 in production should work for you soon. -John
-
I posted on the other thread as well, but this is probably the correct thread. --- Can you reproduce it, ie is it currently happening every time or intermittently? If it's happening intermittently, are you using the same credentials with several different web services apps at once? -John
-
You should be able to set InternalId when creating a new CustomField. There will still be a prefix (eg CUSTENTITY<your id> just like in the UI). If this doesn't work, can you post the request and response SOAP? -John
-
The stack trace you included looks like it's coming from .NET. This means it's your client that is throwing the Exception (not that it's not a problem on the NetSuite server, just that the stack trace doesn't give a lot of diagnostic information). The exception appears to be caused by a null response of some sort. Here are…
-
Serialized items should be in before the end of Beta. The WebServices 2.5 represents parity (and more) with SMBXML. -John
-
You can do a search on Customer without criteria - that will return all your customers. Jobs are not supported yet. -John
-
Can you be more specific about what you want to do via Web Services? Eg, what records you need to add/update/query? -John
-
What are you using to generate the SOAP?
-
You can also use the Async WebServices API and we'll handle the queueing if real-time response is not a requirement. -John