- 🇳🇱Netherlands ricovandevin
I have the same challenge in a Drupal installation without Migrate Plus so this is probably something in core. It is also not only paragraphs that are affected. For me it is a custom entity type.
The workaround (at least it feels like that) from #9 is working for me. But IMHO it would be nice if we can extend / refactor the Migration Lookup process plugin to make it return that part of the destination IDs array that we can directly "feed" to a destination property, also in case of translations.
- Status changed to Closed: works as designed
4 months ago 8:30am 6 September 2024 - 🇳🇿New Zealand quietone
Since a solution is given in #9 this support can be closed. The solution is the correct way to get the values you need from the migration_lookup plugin.
This was re-opened with a suggestion about changing the migration_lookup plugin. That is a discussion for a separate feature request issue. If that is what is wanted, open a new issue. Also, be are that there are several issues to improve the migration_lookup process, including a re-work, #3246666: Deprecate migrate_lookup and replace with cleaner process plugin → .
And a reminder that the Drupal Core issue queue is not the ideal place for support requests. The 'support request' option is there for filing support issues for contributed modules and themes. There are several support options listed on our support page → (Community > Support at the top of Drupal.org) and there is Drupal Slack → . You may get better replies in one of those places.