entity_lookup/generate on a field that has more than one entity refereneced

checking this!

if you have 2 vocabulary always there's one what is by default to store the new item, so in the migration'll take that, but I tested that and a exception is thrown because in entity_lookup plugin there's a extra reset function, so I removed this and works!

@jaysonjaynes, you can check this blog, maybe it can help you with your migrations template, ...: https://www.mtech-llc.com/blog/ada-hernandez/how-migrate-images-drupal-8... and https://www.mtech-llc.com/blog/ada-hernandez/entity-lookup-generate-migr...

Let's add a kernel test for this where the destination field has two term bundles possible for it. Back to NW for tests.

So glad this is being discussed. I am running into the same issue. I've tried this:

  field_profile_department:
    -
      plugin: entity_lookup
      entity_type: node
      bundle: department
      source: '@_prepare_dept_titles'
    -
      plugin: entity_lookup
      entity_type: node
      bundle: program
      source: '@_prepare_program_titles'

But it only records the last entity_lookup processed.

EDIT: I realize now my problem is slightly different than the origin of this thread. I have two columns in my CSV that are being migrated into one node reference field with two possible content types. So the hard part is already done before the migration. I just need it to migrate both sets of references into one field.

In my case, Entity Generate was being called with an array for $value and not a single value. The patch iterators over the passed values. It can then cope with all cases where entities are missing or present.

Part of example migration configuration .yml

process:
  field_a:
    -
      plugin: callback
      callable: unserialize
      source: field_a
    -
      plugin: entity_generate
      entity_type: taxonomy_term
      bundle: vocabulary_machine_name
      bundle_key: vid
      value_key: name

somersoft: I had a similar issue like you; but with my own custom process plugin. Adding

  /**
   * {@inheritdoc}
   */
  public function multiple() {
    return TRUE;
  }

to my custom plugin resolved this for me. I'm not saying you haven't collided with a bug, I'm just saying that in my case changing my migration process plugin solved it. If you want this fixed, I suggest creating a new issue with your patch.

@Kobb: did you ever find a solution to doing lookups across multiple content types?

There's sub_process to cope with arrays. And there's the recent SingleValue and MultipleValues that could also help. Still needs work because needs tests.

I'm going to suggest this is fixable with one of those solutions. I'll probably be proved wrong, but let's see if we can cleanup the issue queue.

@seth.e.shaw: No. I ended up creating a new field to import the second entity reference.