FIM newbie here.

We have a situation where the HR source provides the user IDs and their manager IDs. Quite normal.

The kink is that many managers are "external" and their IDs are not present in the HR file but exist in AD.

An example 3 line file could be

UserID,FirstName,LastName,ManagerID,Title

123,Joe,Soap,X123,Manager

345,Chris,Spalding,123,Worker

678,David,Soul,123,Worker

Joe Soaps manager identified by X123 exists in AD as do all the other 3 users. The person identified by X123 just isn't present in the HR provided file. So the 'natural' use of anchors and references fail. It is impossible to push External people into the HR system. However,  All AD entries containing IDs are projected/joined into the MV and onwards into the Portal.

Is it possible to build a rules extension on import to get the "manager" via MV search using the key ManagerID?

I was hoping the following might be possible.

Invent a MV attribute to hold the manager reference called myManager type reference.

With the advanced attribute flow rule import to attribute myManager with flow rule XYZ

In the C# code

get the CS.ManagerID

<somehow get the MVobjectID of the MV entry having UserID = CS.ManagerID>

push the MVobjectID found into myManager

and then flow myManager to AD manager and Portal Manager attributes.

I am not sure if it is possible/would work.

Is it possible to grab a MV objectID with FIM C# methods?

Is it possible to work with reference typed attributes with flow rules?

Just what methods are available to work with the MV in C#?

1. This is very simple, out of the box function.

In HR MA, edit the attribute managerID to be reference and map it to the manager attribute in MV. The rest is taken care off.

2. It is also possible to use the ManagerID to query the MV in .NET and populate the manager with the DN. In this case, DN from AD has to be flown to MV first.

So you look for any object in MV whose EmployeeID matches the ManagerID, then take the DN and populate Manager filed with it.

here is a Blog that explains that. http://blogs.msdn.com/b/therabournidentity/archive/2008/04/29/miis-ilm-code-experiment-populating-the-manager-field-in-active-directory.aspx

Again, I would use the out of the box functionality.

Thankyou for the pointer to the code. The out-of-the-box does solution as you describe does not solve the problem as the HR managerID references point to IDs only visible in the HR connector space. Whole point of my asking.

I am pleased there is away of searching the MV with C#.

That blog exports to AD. If we could use something similar to export a manager to FIMMA I would be happy.

All things considered I think we are forced to use two Sets. One for Users with Manager and another for Users without Manager. When Transitioning into the Set of managerless users WF runs which adds the manager somehow, most likely via Powershell Activities... which then causes the Transition into the with Manager Set and so on...

• The out of the box works and it is designed to accommodate these scenarios.
• ManagerEZID is the same as Manager ID.  This is the HR MA
• Double click the MA to edit and select "Configure attributes"



• Select the ManagerID Attribute and Click Edit

• Select "Reference (DN)" from dropdown and then OK
• Now go to "Configure Attribute Flow" and Map Manager ID to Manager (Inbound)

• Lastly, map Manager from Metaverse to Maanager in FIM MA

With the code solution, it works like this

• Map manager to AD, as described in the article.

• Map manager --> manager (Inbound from AD to Metaverse)

• Map manager --> manager (Outbound from Metaverse to FIM MA)