Issues with converting published webservice to Mx5
1
I have come across an issue with published webservices when upgrading a project to Mx5. It relates to the Return Value when the return from the microflow is a List of an Object. In this case, the return type mapping has all attributes of the returned list selected (whereas in Mx4 I had only some attributes being returned), and all attributes from related objects are now deselected (whereas in Mx4 I had certain attribues of related objects being returned). This has broken a wsdl based integration. It also throws errors where the new mapping now tries to return empty date-time attributes which were not included in the original mappings. The solution is to reselect which attributes should be included in the Return Value. This is a one-off task to restore the mappings, but I hope this will save others having to find the cause of any issues after upgrades.
asked
David Sanders
4 answers
2
We have fixed this issue. The fix will be available in our March release.
answered
Pieter van Balen
1
Received and reproduced, thanks! This is clearly a conversion problem on our side. We will solve it, but I'm sorry it has to wait a little; probably it will be fixed in the March release or otherwise in the April release.
answered
Pieter van Balen
0
David, thanks for reporting. We will investigate this and come back to you.
answered
Pieter van Balen
0
David, could you please provide (part of) your Mx4 project? So far we couldn't reproduce this issue.
Please email to pieter.van.balen@mendix.com