Because the client just sends two Contact
objects to the server, the server does not know what objects needs to be put in what microflow parameter.
With two different object types the server can match the object type on the type of the parameter.
In future versions we will switch to using named parameters thereby solving this problem.
Hi Jaap,
we are doing a lot of similar things at our current project. We've made quite complex wizards but the only way to create them was by using extra objects like 'processtep' or 'combination' that are used as root dataviews.
We set the necessary references to these 'in between' objectswith microflow and are thus able to create the mentioned combinations (when the user closes such a wizard we delete these objects to keep our database neat)