Sometimes could be that you import items and after the import process ended, some of the items failed or where skipped in the import process and you want to know which items where those.

Now in the UI you can see how many items where not processed, but would be great to be able to list those items, so you can see which items where not imported and why directly from the UI.

Comments

edurenye created an issue. See original summary.

cosmicdreams’s picture

cosmicdreams CreditAttribution: cosmicdreams commented

I've been looking into how this might be done myself, with the intent of deleting anything from the Drupal site that is having data migrated into that it's apart of the source data. But it appears that migrate tools is only comparing the counts of records it has locally and the records from the source. So it doesn't actually know (on a row by row basis) what data is in the database that isn't apart of the source.

If we want this issue to be about adding that tracking of destination data (that is no longer available in the source) and then providing a list of everything that isn't that would be cool.

edurenye’s picture

edurenye CreditAttribution: edurenye at ENDPHASYS Technologies commented

We can get this information from the source_row_status field in the migrate_map tables of the database. I don't think we need to track anything extra.

edurenye’s picture

edurenye CreditAttribution: edurenye as a volunteer commented
Assigned: Unassigned » edurenye
Related issues: +#2891633: Add support for union in views data

I can't une 'UNION' in the hook_views_data() as it's not supported by Drupal, so since we can't have views for each migration, I'll try to create a Controller and query the data like with the rest of lists, now I get why they didn't use views, but I think core must support unions, I opened an issue for that, but that might take some time, so I'll use a controller.