3936442

If you know their internalIds, yes. Otherwise they will not be returned in search in endpoints for which they do not exist. -John

Another solution is wrap your NetSuite calls. This method assumes you have a NetSuitePortType m_port in your application class. public WriteResponse nsAdd(Record myRecord) throws SoapFault, RemoteException, InterruptedException { final int MAX_RETRY_COUNT = 3; int retryCount=0; WriteResponse toRet=null; for (boolean…

I think your internalId is wrong. Use the full uppercase name of the field (eg CUSTBODY12). Go to Setup->Customization->Transaction Body Fields. Find the custom field you are you want the "ID" column is what you want to set as the InternalId. Good luck, John

CustomRecordSearch is working, and your code looks correct. 1) Are you inputting just a number for internalId? 2) Can you post the SOAP? Thanks, -John

This is tracked by issue 169905. Are you sure you are setting the OAUTH header correctly? Can you post your http request headers (blank out the consumerkey/shared secret)? -John

What does the http traffic look like? Is the header being sent the same way over the wire? -John

The %26 represents an ampersand that is url encoded the & -> %26 -John

Are you setting any cookies on the way in? If so that's probably the cause of the problem -John

It will break as soon as you upgrade your code to the latest endpoint (not when your account is upgraded). The new way is actually simpler and more complete. We've exposed the "state" record. Simply do a "getAll()" on the state record and use the shortName. This also supports user created states. -John

Can you change xsi:type="nsCommon:SearchStringField" to xsi:type="nsCore:SearchStringField" The SearchStringField type is in core.xsd. -John

You shouldn't get the same error with the NetSuite 2.6 wsdl/XSDs (once they are out of beta). In the meantime you can use Axis. I believe Axis loads the WSDL first and thus has all the imports done. -John

The example in the SuiteSource directory is a hybrid of pure XML and OO. It's not fully dynamic in terms of generating the WSDL on the fly, but it wraps up the major objects (like RecordRef, Record) and handles Serialization for you. It's based on NuSoap and PHP5. -John

You don't as your code will continue to work. It's helpful for our internal tracking if we know that a customer reported an issue, which is one reason we ask for a case to be entered. -John

Customer.EntityId Right now we don't auto-set the entityId field based on first/last name because it's a simple concatenation. Please enter a case to the effect of "Setting firstName, lastName and isPerson=T causes USER_ERROR - please enter a value for Customer ID." -John

Have you changed the type of a CustomField? What happens when you try to do this update in the UI? Does the field with "Richard Graham" get blanked out before you save? -John

Can you file a case? Send in the SOAP you submitted and this result. -John

There is probably 1 specific record that is causing the problem. Is there any way you can narrow it down (ie try searching within a date range). BTW, just curious, what does your app do? Paging all the way through 12K records is not a recommended use of WebServices. -John

Is the EPOS system is using NetSuite as a System-Of-Record and syncing every day? If so, we have added the "getDeleted()" operation which together with normal searches on dateModified searches provide for much more efficient syncing. As for the problem you are seeing, again it's probably caused by 1 odd record in your…

Make sure to put the date and time of the error in the Case. BTW, is this still happening?

You should not see inactive valures returned on GetSelectValue. The idea behind getSelectValue is to mirror what you would see in the dropdown if you opened up a new record in your web browser. -John

Thank you for the research on this one. There is clearly a problem on NetSuite's side - please file a case. -John

Can you post your request and response SOAP? Thanks, John

You are correct we return dates with timezone information. EG 2003-11-12T21:35:00.000-08:00 Where the Timezone above is PST. This is the W3C date format. Any decent date/calendar object will convert this to local time for you. Likewise, when adding or updating, make sure your date object serializes the timezone and there…

>if I submit a createdDate of 2006-11-03 01:00 am CST, you will internally have a value of 2006-11-02 11:00 pm PST Both of those representations are the same number of seconds from 00:00:00 UTC on January 1, 1970 and that is what we store. > Also, what happens with items that are specific only to the day We store the day…

You need to use search for most records. I copied this from the PHP sample application - http://www.netsuite.com/portal/developers/resources/suitetalk-sample-applications.shtml [CODE] $itemSearch = new nsComplexObject("ItemSearchBasic"); // Option 1 - instantiate an nsComplexObject and set fields. Both options produce the…

This should get you started http://suitesource.netsuite.com/s.nl/it.A/id.39/.f?sc=2&category=17