Employee Type and Anchor Attribute
Hi, We have a typical scenario that there are 3 employee types: full-time, contractors, temp. It appears that only full-time and contractors have an actual employee number; temp's do not. Of the 11 connected systems, about 4 require all employee types to be replicated, while others may only require full-time or contractors. How would I link the objects together (using the anchor ID)? Can I have the first anchor ID = employeeNumber and another anchor to something like samAccountName? Will FIM try a match on one, then try another match? Thanks
October 12th, 2010 11:44pm

The anchor is not an attribute to link objects together - ACCROSS connected data sources. The sole purpose of the anchor is to link a CS object with the partner in the connected data source. What you should have (ideally), is a Correlation ID. It might be that you can use an anchor for this - it depends... For more details on Correlation IDs, see the related design concepts document. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
October 13th, 2010 2:30am

Yes, what I meant was the attribute that is used to Join objects together between system (on object update). So can FIM try match on more then one 'Join' attribute? If for instance Employee ID fails then try samAccountName - for example. thanks
October 13th, 2010 4:41pm

Yes S. Kwan You can user employeeId, sAMAccountname or other attributes that make your objects unique on each connected system. You can use a combination of attributes in your join rules if you dont have one that make this relatinoship. Regards
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2010 6:47am

ah I see, thank you
October 26th, 2010 5:26am

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

Other recent topics Other recent topics