Hi - today’’s mechanism generating a message definition by selecting an entities works nicely – however it ignores that there may be specializations of associated child entities. To cover them properly in imports / exports, you’d have to manually create / change an XSD and create fairly complex mappings.
Please, this must be improved to generate a workable message definition and mappings including spezializations of child objects right from the scratch.
This is a big pain-point for us. +1
I totally agree. Almost two years later this isn't solved yet.