Handling of Extra Attributes in Import Mapping

Issue: How can we manage and store unexpected extra attributes when utilizing Import Mapping for e.g. REST API responses in Mendix, given that static import mappings are incapable of mapping these dynamic attributes? This issue frequently arises in scenarios where the APIs are poorly documented.

Suggestion: Introduce an option within Import Mapping to process unexpected attributes as key-value pair objects and associate them with the main object.