Bug #6684

CSV import fails if qubitParentSlug and qubitParentID are both included

Added by Dan Gillean about 8 years ago. Updated almost 8 years ago.

Status:VerifiedStart date:05/07/2014
Priority:MediumDue date:
Assignee:Dan Gillean% Done:


Category:CSV import
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:


Currently when performing a CSV import with hierarchical data, if both qubitParentSlug and qubitParentID are set in a single row, the entire import will fail. However, there is no reason why this should break the entire import. Instead, we will remove the code that throws the error and stops the import - if both are included, the import will prefer the qubitParentSlug, as this is more likely to point to an existing description in a way that a user would have access to (having a parentID for an existing import assumes that the description was originally imported with a legacyID, and that the user has access to AtoM's keymap table to look up this legacyID and enter it into the parentID column).


#1 Updated by Mike Gale about 8 years ago

This was a simple matter of deleting the throw new sfException() line, as the if/elseif/else structure underneath prefers qubitParentSlug and should function fine. See commit 458f6a470b40541291a950c4aebaae92320acfcd for details (I forgot to ref it in the commit message).

#2 Updated by Mike Gale about 8 years ago

  • Assignee changed from Mike Gale to Dan Gillean

#3 Updated by Sarah Romkey almost 8 years ago

  • Status changed from QA/Review to Verified

Verified in 2x, works as expected.

Also available in: Atom PDF