Modifying AnchorID implications?
Hi, What are the implications of modifying existing AnchorIDs? Assuming SystemA.record1 has a relationship with SystemB.record1, based on a uniqueID....but now SystemA.record1 needs a relationship with SystemB.record2? thanks, SK
May 2nd, 2012 2:37am

Hi, The implications is that FIM Synchronization will detect a delete and an add. If you would change the reference attribute, the objects would be linked. Potential danger is that when the metaverse object deletion rule is set on 'SystemA'. If you would change the anchorId, the delete would trigger a metaverse delete and create a new object. Is that the case? Best regards, Pieter.Pieter de Loos - Consultant at Traxion (http://www.traxion.com) http://fimfacts.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
May 2nd, 2012 3:06am

Take a scenario where a User has an Extension. Users exist as records in AD. Extensions exist as other records in another system; however these Extension records have their own attributes that need to be flown back into the MV and other systems, e.g. PhoneType. So if a User changes their Extension, the User would now need to be linked to another Extension record, and flow back any additional attributes, e.g. PhoneType. Hope that is a bit clearer.
May 2nd, 2012 9:30pm

Take a scenario where a User has an Extension. Users exist as records in AD. Extensions exist as other records in another system; however these Extension records have their own attributes that need to be flown back into the MV and other systems, e.g. PhoneType. So if a User changes their Extension, the User would now need to be linked to another Extension record, and flow back any additional attributes, e.g. PhoneType. Hope that is a bit clearer.
Free Windows Admin Tool Kit Click here and download it now
May 2nd, 2012 9:30pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics