user10648298 Newbie

Please enter a case for this - make sure you include the Saop (second version is better). Your SOAP looks correct. BTW, the CUSTENTITY will be prepended for you, you only have to make the internalId "_TEST" -John

I don't think either would work they way you want. The first definitely would not as you can not retrieve Items of type Group (or kits or assemblies). Try the second and post back the results. -John

I think you want to set the OrderStatus field, not the "Status" field, but that's probably a typo. Make sure that the user you are logging in with has permission to approve salesOrders (ie make sure that user can do this in a web browser). -John

The internalId of the SelectCustomFieldRef is the name of the field (ie CUSTRECORD12). The typeId of the ListOrRecordRef is an integer: For CustomRecords this is a positive number, the internalId of the recordType (a number, 1,2,etc). For StandardRecords, it's a negative number and can be found in the documentation under…

Can you post the SOAP? Thanks, John

This is indicative of having two concurrent client threads share a session. We only allow 1 active request per session to maintain consitency. Is it possible that you have 2 requests "in-flight" at once? -John

We don't support that yet (unfortunately). If you attempted to do this add in the UI, the Item List at the bottom would auto-populate with the contents of the group. Likewise, if your WS request included every item in the group, it would succeed. Supporting groups/kits/assemblies is definitely on the roadmap, but we are…

Not until we support the File record (it's on the roadmap). Until then we return a SelectCustomFieldRef which has the internalId of the image. However, you will not be able to view the image without logging in (so you can produce a URL that would be visible from the outside world). -John

You probably want to use Detach() for this. It's available in the 2_0 and later WSDL.

Parent should be settable on Customer. Have you checked that parent is on your defaut customer entryForm? -John

OK, you are going to need to switch to 2_5 for that. The searchCriteria on a getSelectValue refers to the text of the Select Value - not any related field. -John

Can you Private Message me with Account #'s and Date/Times that this happened (preferably in the recent past)? Eg Login took 10 seconds, Add Customer took 15 seconds on ACCT123456 on 3/26 at 8:15am. I'll investigate on our side and see if something strange happened. -John

Check that all your recordRefs refer to valid records in the NetSuite system. Aside from that, I would need to see the SOAP request/response. -John

If you know the nKey of the item you want, you can just specify it in the itemList / item recordRef. You do not need to specify the RecordType field or the name. So something like this is all you need to do. --- RecordRef myItemRef = new RecordRef(); myItemRef.internalId = "14"; mySalesOrderItemLine.item = myItemRef; ---…

One way would be to tag the items in your system as "partner items" either by using a custom field or a prefix on the netsuite itemId. Alternatively, in v2_5 you could use externalId and do it in one step. First, update your item's externalId to be the partner key or name (must be unique across items) When adding a…

Create a case for this and post the number. Thanks, John

--- "<ns1:baseRef xmlns:ns2="urn:core_2_0.platform.webservices.netsuite.com" internaId="26" type="customer" xsi:type="ns2:BaseRef">" --- Our schema is a little tricky, the get() operation actually takes either a RecordRef or a CustomRecordRef, BaseRef is the (abstract) superclass. --- <baseRef…

We do not return assembyItems yet. We don't return something in search until we support that record and have a full schema for it. If you look at the RecordType enum coreTypes.xsd, you will see an entry for every Record that an endpoint supports. (eg v1_3_2...coreTypes.xsd will look different from v2_0_0). -John

Can you post the SOAP?

You are correct. 2_5 will be available when you get the 11.0.4 release. -John

We've actually been seeing this error in our logs and are aware of it. The problem is that we rely on the SOAPAction HTTP header to properly route requests during the phased release portion of our release cycle. The problem seems to be coming from SOAPLite and NuSoap client libraries. Is anyone experiencing this with .NET…

> If I leave the value blank I get this error Are you specifying that the _drivinglicense field is an empty string ("") ? I'm not what client you are using to generate your SOAP, but unless the field is mandatory, not setting the field at all mist solve you problem. Can you post the SOAP? -John

Do a search on SiteCategory without any criteria. The field parentCategory will express if a SiteCategory has a parent. -John

Search has had pagination and 1000 has been the page size limit since v1_0. The recordlist array (returned in SOAP) has never been longer than 1000. Changes for each version are described in the release notes -John

Can you post the error message? In the meantime, make sure that you are including SOAPAction: "login" In your HTTP headers.

NetSuite has sample applications in C# (.NET) and Java (Axis). These are the recommended platforms. The documentation (and links to sample apps) can be found at http://www.netsuite.com/portal/partners/netflex/webservices.shtml Good luck, John

Have you looked at the totalPages and pageIndex? You should have multiple pages. 1000 is the maximum page size, and results are paginated after that. -John

Do a search() on CustomRecord with only the recType set and no other criteria. This will return all of the records. Make sure you have bodyFieldsOnly set to true for performance. Good luck, John

Right now you need to know the internalId. However, you can get the internalId by doing an ItemSearch. Specify the name (probably ItemId) and ItemType, and make sure you specify bodyFieldsOnly=true (since all you really want is the internalId). -John

That looks like an XML parsing error message (just a guess). Can you turn System.Net tracing on in your appconfig file (if you have one)? It's going to be nearly impossible to diagnose this problem without seeing the HTTP response. -John