2 of 2 people found this helpful
yes, that's possible.
Out of the box, HEAT tries to match the "company" attribute with the Org Unit's Name.
If it doesn't exist, it creates a new OrgUnit.
I did it the same way for our departments.
For some reasons I had to create link fields to get it working:
1) create a relationship in the Employee object (if it doesn't exist)
2) create a link field referring to this relationship, e.g. XTN_DepartmentLink
3) Map this field in your LDAP Import:
4) Start an Import and see if it is working fine.
thank you. I notice that the location link field on Employee has the Relationship and Targeted Selection empty OOTB.
I'll create this and try again.