Before CM we had URLs like:
So, the foreignSource was set in the URL. CM migrated this foreignSource to the name element and it is correctly displayed in the new UI, but unfortunately this name/foreignSource isn't reflected in the URL anymore. This results in a requisition with a new name and when migrated from 29.x in a duplication of all nodes defined by this external requisition.
The attached screenshot is an example. This should result in a requisition/foreignSource named "MyForeignSource" but this will create a requisition named "vmware-192.168.42.42" which is totally wrong. Existing detectors/policies defined for "MyForeignSource" will not match anymore and all nodes are imported again with the wrong foreignSource.
I don't know if this problem is specific to the VMware requisition or other external requisition types are affected as well.
VMware path handling is here:
I'm not the ne UI expert, but I think this needs to be reflected somewhere here, right?