EntityReference field migration

Try specifying the sourceMigration as the machine name of the poll migration - not an array, and not an empty string.

No further response.

I'm getting this too. I believe it's giving me one failure message for each time the "Story" node doesn't actually point to a "Poll" node (my nodes are actually different types, but the pattern is the same).

I've seen another thread where they suggested that the default value would take care of it, but that hasn't worked so far!

The field isn't required in the D6 source system or in the D7 destination system. Could this be a bug in the handler for node reference fields?

Let me add some detail. In my case "Song" refers to one or more "Composers". Here's my field mapping:

    $this->addFieldMapping('field_composer', 'field_composers')
         ->sourceMigration(array('Composer'))
         ->defaultValue(null);

and the error:

DOException: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'field_composer_target_id' at row 1: INSERT INTO {field_data_field_composer} (entity_type, entity_id, revision_id, bundle, delta, language, field_composer_target_id) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => 8621 [:db_insert_placeholder_2] => 8621 [:db_insert_placeholder_3] => song [:db_insert_placeholder_4] => 0 [:db_insert_placeholder_5] => und [:db_insert_placeholder_6] => ) in field_sql_storage_field_storage_write() (line 448 of /home/groupanizer/domains/misc7/staging/modules/field/modules/field_sql_storage/field_sql_storage.module).

So as you can see it's trying to pass in a null value to an integer field...

Tom

I just did a successful migration of a entity reference.

Let's say I had a couple of articles and people could add a reference to another article. I mapped it like this:

"aricle" is the machine name of the same migration.

I'm amazed this is so simple.

Did it copy over all your records, or just the ones that had a reference?

Hey guys,

In case anyone else finds this by searching, here's a tiny patch that fixes the underlying bug in migrate beautifully:
http://drupal.org/node/1805184

Cheers,
Tom