1. Chad Edwards
  2. PowerBuilder
  3. Thursday, 19 April 2018 21:09 PM UTC

I am working on an application that is currently running in PB 12.0. We are wanting to migrate it to PB 2017 R2. The code migration was easy enough, but when I run the application any web service that I call that has values that are of data type "double" does not get those values. Instead those items in my result structure are set to NULL.

I created a new web service in .Net that returns a class with three properties: two doubles and a string. The then created a simple PB test class to call that service. When the service is called the result structure has the string value populated, but the two double values are set to NULL instead of the values that were hard coded in the test service.

Has anyone else ran into this? Is this a known issue?


Kevin Ridley Accepted Answer Pending Moderation
  1. Friday, 6 March 2020 14:09 PM UTC
  2. PowerBuilder
  3. # 1


 I don't see where you mentioned if you are using the EasySOAP or .NET engine to consume your WSDL and generate proxies.  If you are using EasySOAP, try the .NET engine and rebuild your proxies.  Since it sounds like you can control the service itself, worse case scenario, you can always have it return a string if need be, and you can convert it to double in your code.  Once you move up to PB2017 or 2019 (if you haven't migrated yet, why wouldn't you move to the current instead of 2017 R2?) you can use the HTTPClient as others have said.  It will return XML, so you won't have issues with datatypes, but you will have to parse the XML.  Please see my reply to Eyal on the age of EasySOAP and .NET engines.  Appeon has moved forward with the HTTPClient as the default to handle SOAP and will not be enhancing EasySOAP or .NET engines for SOAP.

There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 5 March 2020 21:13 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chad;

  It could be due to the fact that ... a PB "Double" is really an XML "Float" data type and that this mapping is not being done correctly between the WS and the PB Client.

  Have you tried replacing the Double with either a Decimal, Long or LongLong data type instead in your returned data definition?

Regards ... Chris

There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 5 March 2020 12:26 PM UTC
  2. PowerBuilder
  3. # 3

EasySoap engine is extremely old and has not been updated or received bug fixes in many years.  Can you reproduce the problem using the new HTTPClient object: https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/236-call-soap-web-services-using-httpclient-object

  1. David Peace
  2. Thursday, 5 March 2020 16:17 PM UTC
Also, you say you are using PB2017R2, is there a reason for not using PB2017R3? Certainly we have found the HTTPClient to be easy to use for web service calls.
  1. Helpful
There are no comments made yet.
eyal hadad Accepted Answer Pending Moderation
  1. Thursday, 5 March 2020 06:25 AM UTC
  2. PowerBuilder
  3. # 4


I'm facing something like your problem.

calling to a web service that is an EasySoap engine , and he should return a structure that have a few properties and all of them are returning with null value.

I check with the developer of the web service and he said that the are returning fine.

He created a small wcf test window and checked the values and they all return OK.

any suggestion for this issue ? 

Thank you,



This is how the answer look like...