I
ian.thomas
Hi,
I've been looking at the web part generation within FP 2003 with a view to creating a simple web part that integrates with some web services that I have (one that's straight ASP.net and another that was generated by Biztalk (2004) in order to push information into a simple orchestration). The problem I have is that although I can follow through the amazon example on the sharepoint tutorial OK whenever I try to create a datasourse pointing at one of the webservices running locally I hit a problem. Essentially the parameters to the webservices don't show up. Whereas with the example you can see all of the parameters that you need to pass to the service once FP has scanned the WSDL in the case of my services it finds the operations but there are either no parameters listed or only the name of the complex type that wraps up the parameters you need to send. I've checked the same web services using InfoPath and IP works fine against the same WSDL (i.e. finds operations and parameters).
Is this a fix pack or something that I need to apply to get this to work?
Thanks in advance
Ian
I've been looking at the web part generation within FP 2003 with a view to creating a simple web part that integrates with some web services that I have (one that's straight ASP.net and another that was generated by Biztalk (2004) in order to push information into a simple orchestration). The problem I have is that although I can follow through the amazon example on the sharepoint tutorial OK whenever I try to create a datasourse pointing at one of the webservices running locally I hit a problem. Essentially the parameters to the webservices don't show up. Whereas with the example you can see all of the parameters that you need to pass to the service once FP has scanned the WSDL in the case of my services it finds the operations but there are either no parameters listed or only the name of the complex type that wraps up the parameters you need to send. I've checked the same web services using InfoPath and IP works fine against the same WSDL (i.e. finds operations and parameters).
Is this a fix pack or something that I need to apply to get this to work?
Thanks in advance
Ian