We have a SQL Table of users and their managers as main source to MetaVerse.
The table is provided by HR and gives the ids for all the INTERNAL users + managers.
However, some of the INTERNAL users may have EXTERNAL managers and these manager ids will not exist in the Sql table as "user ids".
In this case FIM will flow a null to manager field in the MetaVerse as it cannot find (dereference the external manger's id)
All is not lost, all managers should have AD accounts. The manager's id not in HR table can be found in AD 99 times out of 100.
What I want to know is the best strategy to fill in the MV manager attribute when null by getting it from AD. What confuses me is the manager being a 'reference' field. This fact may limit my options.
What if I wrote some C# import attribute flow rule for the HR MA, is it OK just to push the DN *string* of the manager found in AD into MV:manager attribute? If not what should this C# code do??
What is best way to cover this hole, I am sure we are not unique in this situation?