Content Onboarding: Support the import of link entity field data in the Relations mapping

How: When selecting the Relations mapping scope, you should be able to map not only the link type, but also the link entity field data for the link entity associated with that link type.

Why: Currently we cannot use Content Onboarding to upload link entity field data unless it is a link entity associated with the main product-variation mapping in the integration model using the Product-Variation mapping scope. In the case of item-item relationships or other non product-variation relationships you can only import the link relationship itself using the Relations mapping scope, but cannot import the link entity field data.

Link Entities are a commonly utilized concept and should be supported by Content Onboarding for more than just the main product-variant relationship in the integration model.

For Who: Customers and Partners (really anyone who needs to load this data into an environment)

Impact: This would decrease the amount of time spent on work arounds such as custom extensions to upload link entity field data at scale. This would also decrease load times for data of this kind by utilizing the increased speed of Content Onboarding. For customers with large amounts of link entity field data (hundreds of thousands to millions of rows) the data load is currently untenable with existing approaches.

Additional context:

Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.