I gather that it doesn't work right now, but I'd like to get the background needed to help fix/implement it. So far I've had brilliant success importing single value fields, but now I've got a multi value text field, and it seems to be trying to create a node per each value (instead of mapping all of the values to one node). So, what's missing, and where do I start poking?

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Title: Please explain importing CCK multiple value fields » Document importing CCK multiple value fields
Component: Code » Documentation
Assigned: Unassigned » mikeryan
Category: support » task

See #432618: Help Migrating to a Multiple Value Field. The migrate module depends on having the content set view contain one row per node, so including a join to a table with multiple values per node is not going to work, you need to handle multiple values in your prepare hook. This needs documenting, so I'm putting in as a documentation task.

robertdouglass’s picture

robertdouglass commented

Ah, ok. Looking forward to that.

robertdouglass’s picture

robertdouglass commented
Status: Active » Closed (duplicate)
hunt3r’s picture

hunt3r commented

I'm in the same boat as RD.

My view looks good, I've had to do two joins to get to where I have the drupal uid associated with the content I need, Basically I'm bridging a simple joomla profile gallery module to a CCK multi-imagefield. The legacy data is one row per image. I'm willing to accept that all photos will be pushed into one node in the migration, however one node per image is crazy, I need documentation on the prepare hook, but how do I construct such a hook?

"Map fields in the Source recordset to properties in a Drupal object. More complex fields such as multiple value elements need to be handled in code using the prepare hook."

Any help here would be fantastic, I can probably get my employer to drop 200.00 into an answer to this.