My Stuff
Comments
-
How does that record look in the browser? Specifically, does it give you an error message for that field? -John
-
Sorry, it got folded into another one, try 156764
-
Unfortunately, not right now. It is an enhancement - you can vote for enhancement 156816. In the meantime you can call "getCustomization()" on customRecordType and that will return both the internalId of the type and its name, from which you can build a Map of id to inernalId, etc. -John
-
I don't understand your question completely, but let me try. Web Services: A Secure Web Services capable library like Axis or .NET that can connect over https to NetSuite. CSV Import: You need to log in to the application via a web browser to use CSV Import. ODBC: You must download our driver and be able to connect over a…
-
What you want to do is add the field to the NullFieldList so.setNullFieldList(new NullField(new String[]{"custbody_field2"})); -John
-
Sent you a Private Message. In addition, one way around this problem is to use Advanced Search. Create a search with only the columns you need in the browser. Reference this search in Web Services and add criteria dynamically (eg manufacturer = Hitachi,manufacturer = Seagate). -John
-
I assume you are using RequestLevelCredentials. If not, you can just use searchMore(). That will live as long as your session (15 minutes after the last request). It's not taking 15 minutes to get a page of 50 search results, is it? Another possibility is that someone else (or a different thread) is logging in with the…
-
1. CSV - It does not sound like CSV is a good solution for this problem. 2. WS - This is probably the best solution. From your existing configuration server (or a third server), write a web services program to read from the configuration server and import into NetSuite Add/Update calls. 3. ODBC - ODBC is not writable, you…
-
Are you searching for Customers? If so "BodyFieldsOnly" is true by default. In this case salesTeamList should be null. Either search with BodyFieldsOnly as false or do a get on the Customer Record. If you do a get() on a customer record, salesTeam should be populated. -John
-
You want to create a LotNumberedInventoryItem... eg LotNumberedInventoryItem itemToAdd = new LotNumberedInventoryItem(); -John
-
Here's an example from the online help for transactions (salesOrder) it's very similar for other records. The difference here is that we are setting the customFieldList on the SalesOrderItem, where for an InventoryItem you would set it directly on the InventoryItem. SalesOrder so = new SalesOrder(); RecordRef entityRef =…
-
You can search a transactionSearchBasic specifying the internalId. The returned record will be of the correct type. -John
-
No, unfortunately CustomRecordSearch does not yet have joins on it. I know you don't have 2008.2 yet, but if your integration is search heavy I strongly recommend AdvancedSearch. It's more efficient and has the capabilities you need. Do you have a Sandbox, Beta or Testdrive account to develop against? It seems a shame to…
-
Also, if you can build a savedsearch in the UI that gets you what you want, referencing it via advanced search will be a performant way to accomplish this. -John
-
I'm not sure I understand, if you only get 200 back on your first page, doesn't that essentially accomplish the goal of "top 200"? Also, if you use AdvancedSearch and reference a savedSearch that has a sort, then setting you pageSize and only looking at the first page will have the same effect as a "top 200" with a sort.…
-
Do you have the SOAP Request and Response? Do they show up in the integration reports? -John
-
This is issu 155730 - please file a case and ask for it to be attached to this issue so you get updated when it gets fixed. -John
-
I think you need to use TransactionStatus, not SalesOrderStatus, for search. Thus <SOAP-ENV:Body> <ns3:search> <ns3:searchRecord xsi:type="ns2:TransactionSearchBasic"> <ns2:status operator="noneOf"> <ns1:searchValue>_salesOrderClosed</ns1:searchValue> </ns2:status> <ns2:type…
-
I think you want to use synchronous search and (_service.search()), set bodyFieldsOnly to false (since you want the pricingMatrix) and shrink your page size to 20-50. If you are experiencing a timeout it may be client based. We never return timeouts for individual operations once they start (sessions can time out, but you…
-
Is it the same error? Does the search request show up in the integration reports? Do you have the SOAP request/response? I ask all these questions because you are doing a very basic search (CustomerSearchBasic with no criteria), that works on our test accounts. I think your best bet is to file a case support. In addition…
-
Login, logout (to destroy the session), login. c.login(); c.logout(); c.login(); -John
-
It seems like it's having connectivity problems, can that server reach webservices.netsuite.com (what happens if you put that URL in a browser on that server?) -John
-
We need the item update SOAP that isn't working. If you or the integrator can get it, file a case and we can try to reproduce it from there. -John
-
You need to set BodyFieldsOnly to False in the Search Preferences. Just search for BodyFieldsOnly in the online help. -John
-
You want to do a Customer search first using lastModifiedDate, and keep track of all the internalIds. Then you want to do a CustomRecord Search using the Customer field on your Account Custom Record as a criteria and "anyOf" the internalId's from Query 1 as the search value. Alternatively, and I highly recommend trying…
-
They are very similar performance-wise. The advantage with get is that if there are additional criteria you wish to filter on in your client (or if your client will select a subset), then you don't waste time retrieving records you don't need. In terms of raw number of records, getList and full search are comparable. The…
-
First try rebuilding your client libraries. Second, is this repeatable? If not, can you point to specific times when it happened? -John
-
We need the item update SOAP that isn't working. If you or the integrator can get it, file a case and we can try to reproduce it from there. -John
-
Item Groups are not yet supported in Web Services. If we don't support adding/updating the record we also don't support returning it in search. This is enhancement 91537 - please vote for it. -John
-
Yogesh is running java code on his client computer - when you say "running a script" I assume you mean a Server Side Script that runs on the NetSuite servers. It sounds like a different problem. Did you get a ticket # back? -John