RELATED IDEAS
Request to keep the classic Excel Import functionality available (or provide an equivalent simplified option) in the new UI
In the new Inriver UI, the Excel Import functionality appears very similar to the Content Onboarding tool, while the classic Excel Import (as in the old UI) has been marked with the label “(legacy)”. This creates uncertainty among users and customers about whether the traditional Excel Import is being phased out.
The classic Excel Import is widely used by customers because it is:
simple,
fast to use,
easy to configure,
and does not require Content Onboarding–style mappings or onboarding steps.
The majority of customers still rely on the classic import tool for routine data updates. The Content Onboarding–style import is powerful, but often unnecessarily heavy for simple recurring tasks.
Thank you for the detailed input and for the votes behind this idea. We've taken all of the feedback into consideration, and we put an extra focus on the simplicity of the legacy Excel import when shaping our new import. It isn't generally available yet, but it will become available for early access, and we'd encourage you to try it then and tell us how we can simplify it even further.
Hi everyone, thank you for the feedback. The Excel Import (Legacy) as it´s called in the new UI will not disappear by the end of the year when we will sunset the old/legacy UI. It will remain in the left-side navigation rail until further notice. I am adding @Joakim Larsson here to comment on the plan for Excel Import (legacy), and you can share continued feedback to him.
Another import difference between the new and the old importer is that the old one could create new Items if the sysID was empty in the importsheet. This gives a quick way to make copies of existing Items based on an export, eg with a few changes. Also import without a key was possible when some customers dont have a unique key to import on.
Absolutely agree with this. Have been trying to find simple Onboarding procedures, but to my opinion there are too many errors/messages/manual steps which for 'normal' users are not easy or even unexplainable. As an Admin I have been trying to make fool proof ways of working, but I failed on many occasions.
Totaly agree! When using Excel just for mass-updating content according to the exact data model for the entity, there should be no reason for mapping data. Legacy function is 100% sufficient for most users and must remain as-is.