RELATED IDEAS
Source file mapped fields view in Content Onboardingg
How: Add an additional view that only shows the fields from the uploaded source file
Why: Because I want a simple view that only shows me the fields from my source file rather than and few hundred fields form the datamodel and then try to find unmapped fields from the source file
For Who: Content Onboarding users
Impact: Timesaver
Additional context: I don't understand the logic of displaying all fields from the Inriver datamodel (or only mapped/unmapped) as my focus is on a file I'm trying to import with an x-number of columns and I want to be sure that these columns are mapped. I don't want to crawl through the entire field list or having to open the field-selector dropdown to see which fields are still unmapped.
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.
This is on the roadmap and will be exposed via the new Import UI that will be available for Early Access in the near future.
Thanks for this — you're right, and we agree.
The current view was designed around the data model (ensuring all mandatory fields are mapped), which made sense at the time. We've since realized that import users need the inverse: start from your source file, not hundreds of data model fields.
This is actively in progress and prioritized — no firm date yet, but it's not sitting in a backlog. More to come.