The FK from the import table to the entity is [created here](https://github.com/civicrm/civicrm-core/blob/master/ext/civiimport/Civi/Api4/Event/Subscriber/ImportSubscriber.php#L90). This is based on the User Job type, which is mapped to the entity for regular imports, but batch imports have a User Job type of search_batch_import, which obviously does not map to an entity. The end result is that the Contribution ID in a batch SearchDisplay is not linked to the contribution, though maybe there are other impacts as well. To fix, I think we could either make a new set of types like search_batch_import_contributions etc or we could add another field in User Job specifically to hold the entity. The latter might be more robust for the long term and it feels like would be minimally disruptive if we added it now while this is still new. @colemanw thoughts?