Hi,
please add a pub.flow:savePipelineToFile and pub.flow:restorePipelineFromFile after the getTransportInfo invocation.
Use the same Filename as Input for both Services.
This will not harm your normal processing (except for a very small delay), but gives the possibility for debugging.
After the service has been invoked the first time after the change with real data, disable the savePipelineToFile and open the service for debugging and step throuh it.
After the restorePipelineFromFile check what is really in the returned pipeline. There might be undeclared Fields which can be used when explicitly added manually and mapped afterwards.
Please share some screenshots of the above outcome if possible.
Regards,
Holger
#Integration-Server-and-ESB#webMethods