Unfortunately no, we even tested it with appeon analysts and came to the conclusion that it's a bug in the version

FYI: https://www.appeon.com/consultants/consulting-partners

Thank you so much for your help and attention Chris

You are most welcome! ;-)

yes

Very strange. I would now suggest creating a simple test case with a PB.Net WS and WS DWO - and then posting the test case here for the community to have a deeper look at.

I replied with a simplified project, just a connection function and retrieve

Does is work OK if you press the "Invoke" CB?

no, the result is in the first print of the post

Hi Equipe;

I thought so. FYI: Did you know that the WSDW feature is now deprecated & will be removed in PB2022?

In the meantime, it should still work in PB2021 Apps if the WS(s) you are communicating with are still using SOAP based and support TLS 1.0- 1.1.



Did you regenerate each of the WS DWO's DLL (if they are .NET based)?

PB.INI setting ...

[Data Window]

GenerateWSAssembliesOnCompile=YES

debug_ws_metadata=1



Regards ... Chris

hi chris,



so, about the removal did not know yet, but at first we need to solve this current problem.



Regenerate DLLs? at first I use the ones that came with the installation, if that's what I understand.



I made the change inside the pb.ini, I don't know if only that would work, but it still didn't work, just in retrieve that is showing an error and returning this compiled code that I don't know where to adjust or if there is any configuration missing within the server.

Each WS DWO generates a DLL "Helper". The changes to the PB.INI that I mentioned earlier will make sure that the associated DLL that is related to the WS is rebuilt when you perform a Regenerate or Full Build on those DWO's. I'll post a screen capture in a minute. These old DLL's *must* be updated.