Drupal Association members fund grants that make connections all over the world.
I've got a custom entity (with revisions). Entity API generates a key schema for the migration that includes the revision id. This works until I migrate content in a key map, as the entity reference destination handler is passed both the id and the revision id and tries to reference both as target_id.
I created this patch to fix it, but it feels like a hack, and I've not been able to track down exactly what is going on.