Matthew,
Been messing with something similar in the SharePoint Sync client - helping a colleague.
Assuming that the connectors are both coming from the same source and that you want the new connector to join - Make the "wrong" or old connector an "Explicit Disconnector" on the contributing MA.
Then the new connector should join, as the join criteria should be met. Else use the joiner to force the join.
If it all goes wrong and you want to re-connect the old object - use the joiner looking for explicit disconnectors on that MA - once you have the right one change the disconnector type back to normal disconnector.
If you want the MV entry to go, look at the object deletion rule to identify which MA's must become disconnected to delete the MV object.
Hope this helps,
Jon.
-----Original Message-----
From: Discussion for MS IDM tools liks ILM and FIM [mailto:[log in to unmask]] On Behalf Of Matthew Slowe
Sent: 22 April 2015 12:13
To: [log in to unmask]
Subject: How to cause a disconnect
Afternoon all,
If the MV attribute that a CS object originally JOINed based on changes then the default behaviour is for the object to stay joined. However if there is a new CS object which now matches instead, it's unable to (ambiguous-import-flow-from-multiple-connectors).
Is there a way for this new object to take precedence over the original one and force a disconnect to allow the new join to work?
--
Matthew Slowe | Server Infrastructure Officer
IT Infrastructure, Information Services, University of Kent
Room S21, Cornwallis South
Canterbury, Kent, CT2 7NZ, UK
Tel: +44 (0)1227 824265
www.kent.ac.uk/is | @UnikentUnseenIT | @UKCLibraryIt
|