• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 7947 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Importing References in One Identity

ds_walters
over 7 years ago

I've got a SQL HR database with two tables. One table has general HR data, the other has departments. The HR table contains a field department that contains the number of the department in the departments table. Basic foreign key reference. I can import the users into One Identity and I can import the departments but I'm not sure how or where I can flow the reference so that uid_department on the user is set to the correct department as indicated by the HR table. One way I could go it is to flow the number into One Identity on the person object then create a template and I think I can cajole it into selecting the right department and updating the uid_department field. Is there a better way to do this where I can import and it will automatically populate the department properly? If you can point me at any documentation that would good to. 

 

Thanks

Parents
  • +1 over 7 years ago
    Hi,

    Are you using Version 7.1 or later?

    I have set up something similar to this in a test lab with a dummy HRMS database. In mine, the department ID is an autonumber. So, a description of a department might change, but the number assigned to it is permanent. For this reason, the department table sync didn't need to do object matching on any attribute other than the autonumber.

    So I created a virtual property for a custom property as follows on the "HRDepartment to OneIM Department" mapping:

    Virtual Property Name: VRT_CustomProperty03AsDecimal
    Display Name: DeptID in CustomProperty03
    Base Property: CustomProperty03
    New Data Type: Decimal - fix point number

    The object matching rule was added as follows:

    Rule Name: VRT_CustomProperty03AsDecimal_DeptID
    Display Name: Spare field no. 03 <-> DeptID
    Case Sensitive: checked

    One Identity Manager Schema Property: VRT_CustomProperty03AsDecimal
    Target System Schema property: DeptID

    Step 2: on the Person sync, create a "key conversion by reference" custom property:

    Virtual Property Name: UID_Department_from_CustomProperty03
    Base Property: CustomProperty03

    Once you've got this, then you can resolve UID_Department from DeptID.

    One way to do that is translate the DeptID to a virtual property in your Person import, and use that to look up the UID_Department during the sync.

    Another way to do it is by setting a custom property with DeptID from the employee table, and then use a template on the custom property to look up UID_Department.

    I cannot advise which of the two approaches is best to take; the answer to that question depends on factors like, how often does your department structure change and how often do people move from one department to another; how many departments and people do you have....
Reply
  • +1 over 7 years ago
    Hi,

    Are you using Version 7.1 or later?

    I have set up something similar to this in a test lab with a dummy HRMS database. In mine, the department ID is an autonumber. So, a description of a department might change, but the number assigned to it is permanent. For this reason, the department table sync didn't need to do object matching on any attribute other than the autonumber.

    So I created a virtual property for a custom property as follows on the "HRDepartment to OneIM Department" mapping:

    Virtual Property Name: VRT_CustomProperty03AsDecimal
    Display Name: DeptID in CustomProperty03
    Base Property: CustomProperty03
    New Data Type: Decimal - fix point number

    The object matching rule was added as follows:

    Rule Name: VRT_CustomProperty03AsDecimal_DeptID
    Display Name: Spare field no. 03 <-> DeptID
    Case Sensitive: checked

    One Identity Manager Schema Property: VRT_CustomProperty03AsDecimal
    Target System Schema property: DeptID

    Step 2: on the Person sync, create a "key conversion by reference" custom property:

    Virtual Property Name: UID_Department_from_CustomProperty03
    Base Property: CustomProperty03

    Once you've got this, then you can resolve UID_Department from DeptID.

    One way to do that is translate the DeptID to a virtual property in your Person import, and use that to look up the UID_Department during the sync.

    Another way to do it is by setting a custom property with DeptID from the employee table, and then use a template on the custom property to look up UID_Department.

    I cannot advise which of the two approaches is best to take; the answer to that question depends on factors like, how often does your department structure change and how often do people move from one department to another; how many departments and people do you have....
Children
No Data