Migrate message is confusing when trying to reimport already imported entity with --idlist flag

Created on 10 March 2023, over 1 year ago
Updated 20 January 2024, 5 months ago

Problem/Motivation

Migrate message is confusing when trying to reimport already imported entity with --idlist flag.

Migrate message throws a notice stating id is not present in source, but in fact it is present and already processed.

Steps to reproduce

1. Process a migration with drush mim MIGRATION_NAME
2. Try to process single entity data again with drush mim MIGRATION_NAME --idlist=SOME_ID
3. You will receive a notice "The following specified IDs were not found in the source IDs: SOME_ID."
4. Now try to run drush mim MIGRATION_NAME --idlist=SOME_ID --update data gets processed as usual

Proposed resolution

Notice message should include message stating it might have already imported.

Remaining tasks

Update notice message.

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Needs review

Version

6.0

Component

Drush commands

Created by

🇮🇳India Bhanu951

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @Bhanu951
  • 🇳🇿New Zealand quietone New Zealand

    The error message in the Issue Summary is not in core. I searched and found that it is from Migrate Tools. Since this is about updating the text of that message, I am moving this to Migrate Tools.

  • 🇺🇸United States mlncn Minneapolis, MN, USA

    Had to find this issue by searching for "The following specified IDs were not found in the source IDs:" to confirm that the Drupal migration was lying to me. Thanks! It's probably not just the message but the understanding of what is happening that needs to change, that is we don't just change the message text because sometimes it is output correctly as when the view ID truly isn't there.

  • 🇺🇸United States apotek

    In my case, I am encountering this message while attempting to import an item and the import is not working when I specify an id. It only works if I don't specify the id (and yes, my source id is correct). But I do wonder if this is related to having two source ids in my migrate map. Perhaps this option doesn't work if you have two source id keys configured?

  • I'm getting this message as well when trying a single node ID, e.g. drush mim MIGRATION_NAME --idlist=9879.

    Unfortunately, adding --update at the end causes it to barf (although --update works fine without --idlist) with the error . I tried --update=TRUE and it complained that update doesn't take values.

    Any help appreciated!

  • Assigned to apotek
  • Status changed to Needs review 5 months ago
  • 🇺🇸United States apotek
  • Pipeline finished with Success
    5 months ago
    Total: 341s
    #80167
  • 🇺🇸United States apotek
  • Pipeline finished with Success
    5 months ago
    Total: 354s
    #80175
Production build 0.69.0 2024