No, send the em mail from your app.

done talking to myself, off to support

Now seeing different error in same used to work fine code [Code=UNEXPECTED_ERROR] An unexpected error occurred. Error ID: g10xsyw3n12q5wxinaii I'm doing a Customer advanced search returning internalId, entityId & las modified time

This all seems to be related to last modified date and date created formatting and WS. Issues continue. I get a variety or errors when trying to retrieve customers like: NS returned this for Last Mod date (note the year) <listRel:lastModifiedDate>20099-09-05T13:22:36.00007:00</listRel:lastModifiedDate> and An unexpected…

Hmmm, seems better now. If it pops back up i'd guess a corrupt server instance

got this today, 9am PST This notification is pertaining to defect 171163. We wanted to inform you that this defect 171163 (WS>Invoking Search operation will return an unexpected error) has now been fixed and closed in your production account. Please test this in your account and verify that you are no longer experiencing…

We filed a bug on this a few weeks ago (defect 168287). Workaround ... SUMMARY: WS > When adding a Cash Sale record, Cash payment option is not honored and Credit Card details are persistent when credit card information is attached to the customer selected in the cash sale. WORKAROUND: Set the Credit Card fields in the…

custom record search criteria is specified like any other record. take a look at property CustomRecordSearchBasic.customFieldList you set custom field search criteria in there using SearchBooleanCustomField and SearchStringCustomField updates are possible too, like any other record with a custom field list

looks like may be bad date in your NS record? You are able to get some record back but not others? If this sounds right try to identify the offending record edit/delete it

No you can't void anything via WS.

Ah, so you want to call NS WebServices from a script? I've only used external WS endpoints but it should work if NS does no have IP restrictions. You don't put the wsdl url as the first param but the service enpoint URL. A good approach to this might be to do the call from Java/C# and tcp monitor the message and then…

So very funny, one of my clients jsut reported seeing this error too. Same date and everything. I suspect the issue is on the NS side .... I dig a little more and maybe start a case.

Yes this is possible. I've had a couple of occasions to do this. Baiscally you hand construct the message (SOAP?) and use nlapiRequestURL to do the post. If https then CA must be recognized by NS (see script doc)

getSelectValue() returns the internalId & name for standard lists. Otherwise turn on "show internal ids" in UI General Preferences and look up the list in the UI. Now in the UI the internal IDs should show when viewing a list.

Looks like you generated the client libs incorrectly? When I do this I have an additional object, CustomerAddressbookList, to deal with . Here is an idication of wsdl2java (axis 1.4.1) settings and what my code to do the same looks like: <code> <axis-wsdl2java timeout="120000" output="src/main/java" verbose="true"…

mucho gracias

These financial reports can be retieved in an automated way but not with web services direclty. First customize the report an look in the more options tab. Check "Allow Web Query". Now go to the report and where you would choose to export as CSV choose Web Query. This will create a text file for you that contains a url…

Case #829590 Update : TransactionSearchBasic.setPostingPeriod. I think it is now an S2

You'll want to add -a and -w options. see http://dynip.pfountz.com:8080/axis14/reference.html#WSDL2Java Once you get this working you are gonna want to map namspace to package but not required. I usually do this with maven all with maven

For base prices assign "price" record ref with internalId of 1

Use the pricing matrix, sorry don't have an example handy

We're trying to go live with a 3PL integration and our SOAP for inserting tracking #s is failing (the old "do not have permission to set this field" error). Originally, the client was setup with FedEx integration and auto- generation of labels & auto-generation of tracking #s, but we have disabled that. We're using 2008.2.…

NetSuiteBindingStub stub; NetSuiteServiceLocator service = new NetSuiteServiceLocator(); service.setMaintainSession(true); NetSuitePortType netSuitePortType = service.getNetSuitePort(); ((org.apache.axis.client.Stub) netSuitePortType).setUsername(passport.getEmail()); ((NetSuiteBindingStub)…

my understanding is that it is best (performance wise) to do a bodyfieldsonly=true on the search and then do a get or getList to full retrieve cust with addresses and all else

Looks good to me, you might enter a record in the UI and do a WS get to see what NS thinks are the proper values are.

FYI, this issue has been fixed

This appears to be an issue with the A/P filter on vendor payment that restricts the list of Bills that the payment can apply to. This is strangely sticky based on the last vendor payment accepted in the Web UI. This web UI value is then inferred on subsequent Web Service payment posts. The A/P account if set on the Vendor…

BTW, have case 797169 openned

Are you setting the price level reference on the item? setPrice(yourLevelRecordRef);

I works now