Currently, it's possible to create an import/export mapping from json/xml to domain model entities and vice versa, but often, you have to map data from one entity to another entity, for example when converting a persistant object to a non persitant object.
It would be awesome if this could be done with a mapping, just like the current import/export mappings.
Well, five year later, but it can be useful for someone.
Its possible to create one message definition to each entity, and then create an export mapping to the origin entity, and a import mapping to the target entity.
For me, thats solved my problem.
Here, the steps.
Message Definitions
Mapping Entity=>Message.
Mapping Message=>Entity.
And finally the use of the mappings in the Microflow.
I just run into this issue. A vote from me.
I agree with you Bart, after having made a lot of mapping microflows (again) this sprint, you got my vote!
Bump, because I sincerely believe this idea deserves more than 9 votes :)