none
Matching HR and AD records on 2 attributes, then modify the join attribute? RRS feed

  • Question

  • Hi,

    We are introducing FIM into an environment consisting of an HR system and AD, with no so happy data. I know that data integrity is key, but there are people above that want some results....so....

    The only match between the existing HR and AD data we can find is the 'firstname' & 'surname' attributes. Lets assume for now that there are no duplicate 'firstname' & 'surname' attributes in HR and AD...could we join the records on 2 attributes of 'firstname' & 'surname'?

    Once the records are joined, we would then flow the 'employeeID' attribute from HR to AD.

    Could we then remove the 'firstname' & 'surname' join rule and replace it with 'employeeID' attribute join rule?

    Thank you,

    SK


    • Edited by Shim Kwan Tuesday, May 13, 2014 4:26 AM
    Tuesday, May 13, 2014 4:25 AM

Answers

  • Yes, or even leave the name-based join there but lower in precedence than the employeeID one. In practice the problem with name-based joins is not just the obvious one of duplicates but more often that the entry in AD has been created with a preferred first name (e.g. Dave) whereas the HR one has the legal first name (e.g. David), leading to missed joins.

    • Marked as answer by Shim Kwan Wednesday, May 14, 2014 2:55 AM
    Tuesday, May 13, 2014 8:14 AM

All replies

  • Yes, or even leave the name-based join there but lower in precedence than the employeeID one. In practice the problem with name-based joins is not just the obvious one of duplicates but more often that the entry in AD has been created with a preferred first name (e.g. Dave) whereas the HR one has the legal first name (e.g. David), leading to missed joins.

    • Marked as answer by Shim Kwan Wednesday, May 14, 2014 2:55 AM
    Tuesday, May 13, 2014 8:14 AM
  • Thanks Dave
    Wednesday, May 14, 2014 2:54 AM