Keep import functionallity without a unique key in new Importer

How: New Importer cant import Entities without a key. In the old Excel import (now legacy) you can leave the SysID column empty and the importer will the create a new Item and assign a new SyID to it.

Why: Some customers create new Items by exporting Items, do some changes,delete the sysID and then import them, they dont have a unique key on these Items and thus they cant use the new importer. To support this process with the new Imorter they must create a fictive shared key, create a mapping and an integration model. That's way to complex for a simple task.

For Who: For all customers that needs a simple way to copy multiple Items in one go.

Impact: If the legacy importer is removed it will add ekstra enrich time to the process by a factor 10. There is a lot of other usecases where the legacy importer is far quicker to use, this is just one use case. On behalf of our customers we will plea for keeping the legacy importer or at least enable the new importer to be able to create new Items without the demand for a key (and a mapping) to keep it efficient to do simple imports.

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.