No "Unique" Checkbox for any fields using CSV parser and Node processor [#1398076]

Initially I was looking to this mod to emulate user-import from D6, one would think its pretty simple functionality, however the maintainers of ye-olden-days mods that did this stuff felt that feeds did a better job. I'm sorry to say it's been more of a pain in the ass than it should have been. The lack of an on-the-fly mapping functionality means users are now restricted to a single template (good and bad, good for me, bad for them), and adding fields later on is a total crap-shoot.

BUT, the basic import and update of CSV data has proven to be the real issue, because I can't specify any unique fields, either with alpha4 or dev (Jan-06).

The Setup:
Fetcher: File upload
Parser: CSV
Processor: Node (content type is custom with 7 or so standard text fields)

No unique checkbox next to anything, not even "title". Any ideas?

Comments

Comment #1

emackn commented 16 January 2012 at 23:11

Status:

Active

» Postponed (maintainer needs more info)

did you specify a content type to receive the imported data. Also, have you tried the migrate module? http://drupal.org/project/migrate

Comment #2

dafreak commented 22 January 2012 at 23:57

Version:	7.x-2.x-dev	» 6.x-1.0-beta11
Priority:	Normal	» Critical

Same problem. The checkboxes seem to appear and then disappear! Without a unique identifier the importer makes myriad duplicate nodes! Would having a unique identifier even solve that issue? I don't know. Something is looping when it shouldn't be. There may be some kind of HTTP error occurring during the import processing. I get the "% complete" bar which jumps to 19% then 38% then back to 19%! What is going on with this module?!

Comment #3

Xomby commented 22 April 2012 at 18:31

I think this mod has been touted to do more than its fair share. Allowing a user(with privilege) to upload a csv/excel sheet and have it generate nodes with on-the-fly mapping based on the selected content type should probably still be a stand-alone module.

I'm still working this issue out for a client project (which is finished, but currently I'm doing the DB update with feeds myself instead of letting their staff do it, because feeds is just too much of a pain in the ass for this specific task to trust them with), and haven't had much time to look at it, but will be soon... again.