batch importer fails on item already exists but it should not

[Jari Häkkinen]

The scenario:

I have many extracts in different projects. I create a new project that I want to import extracts into. The names I use are partly already in use in other projects (yes reusing names seems strange but hey I want to) so I use the nice 'Item identification' options and set the importer to only look after items in the current project. The batch importer imports the items with new unused names but updates the items with reused names. Refreshing the extract list view will only show the new items not the updated ones since they are not in the current project.

The importer of course fails if I set the mode to create only since it then finds items already in the database.