- Issue created by @khaled.zaidan
- 🇳🇿New Zealand quietone
This is working as designed. The migration map tables track the state of a row after the migration process is complete, they are completely independent of any other database table.
This can be resolved using drush, To re-run the migration and re-import a row that was deleted in the destination use the
--updateflag. - 🇺🇸United States mikelutz Michigan, USA
This is neither reasonably possible, nor desired. The map table is a record of what we did, not something that reflects the current state of the system. More importantly the meaning of destination ids is completely plugin defined. They have no relationship to entities at all, so there would be no way to connect a deleted entity to a map table entry. The issue summary describes a custom workflow and problem that is best solved in custom code, where the custom code is aware of the specific relationships between migration destination maps and entities in use in that particular site.