How to pass optional parameters in a web service task in SSS?

Question

How to pass optional parameters in a web service task in SSS?

Aparna-1

SSCrazy

Points: 2339
More actions
July 29, 2009 at 5:34 pm

#140336

I need to pass an optional string parameter to the web service. Ex: If I pass the value as 01/06/2009 they would send all the meeting updates from 01/06/2009 onwards but if do not pass this value all the active meetings for all the dates will be sent.
Note:In their WSDL file they have defined it as String type though they are expecting a date value.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Paul_J Hall of Fame Points: 3698 More actions · Answer 1

It really depends on the web service and what it expects. It may support passing an empty string or null, or it may even have an overload that doesn't expect that parameter.

Aparna-1 SSCrazy Points: 2339 More actions · Answer 2

I have tried an empty string as well as passing null. I am not getting the expected results back, everything comes up as empty tags.

How to handle an overload that does not expect the parameter because when I configure the webservice task and choose the method, it defaults to the input parameters that it is expecting.

When I used a third party tool like SoapUI and pass the value

as is I get the expected results

and when I say

01/06/2009

it works fine as well.

I need to achieve something similar in SSIS.

Aparna-1 SSCrazy Points: 2339 More actions · Answer 3

APARNA (7/29/2009)
I have tried an empty string as well as passing null. I am not getting the expected results back, everything comes up as empty tags.
How to handle an overload that does not expect the parameter because when I configure the webservice task and choose the method, it defaults to the input parameters that it is expecting.
When I used a third party tool like SoapUI and pass the value
as is I get the expected results
and when I say 01/06/2009 it works fine as well.
I need to achieve something similar in SSIS.

Paul_J Hall of Fame Points: 3698 More actions · Answer 4

Please provide more information. Your code, perhaps the wsdl, etc.

Timothy J Hartford SSCarpal Tunnel Points: 4214 More actions · Answer 5

I don't know your webservice, but a parameter needs to be of a specific type when sent to a stored procedure. The only way to send a null (that I am aware of) is to not configure that parameter. Of course, I push our developers to use Stored Procedures for (nearly) any database connections...

Aparna-1 SSCrazy Points: 2339 More actions · Answer 6

Thank You all, we figured out that it is not an issue with SSIS or the parameter but rather .NET and AXIS incompatability. Because even the code developed in .NET had similar results. It is caused by certain namespaces in the webservices developed at the vendors end.