Can we map attribute with data type string with attribute with data type reference[DN] through the attribute flow of a SQL Management agent

Not sure exactly what you are trying to accomplish, but you can use a custom rules extension to map attributes with an Advanced attribute flow. See if this thread helps you: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/0a92a10f-6949-4a5f-82e2-ecf89711a2c2

Hi there, i'm trying to provision the Active Directory "Manager"'s attibute value from a text file or SQL table that contains "accountNAme" and "ManagerValue" for final user. From the MA properties i have configured the "ManagerValue" as Reference DN and mapped to "Manager" (metaverse's att) attribute through the Inboud Rule at the SR. Once i run the import and Full Sync, nothing is sync'ed to the metaverse, and the preview for the object at CS shows "Applied Delete" Status, and FinalValue "Deleted". Am i missing something good to know here to make it work?

Is the accountname attribute set as anchor? and the managervalue also contains the same anchor value (is exists as separate object within the connector space) when you flow the information to the metaverse is there a reference being built (this shown by a blue linked attribute which you can click on)Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

ManagerValue wasn not containing the same accountName. I just modified to be equals and now i can see the blue linked attribute. So, how can i provision Manager's attribute for Active Directory considering that the Source table needs to contain the Anchor attribute for final user (accountName) and the ManagerValue for her/his Manager, but in almost all the cases both values will be different, right? User and manager in the table almost always are different. Thanks in advance.

Oh i just got it. The value for Manager at the SQL table is one value from the Anchor attribute, and it refers to the final Manager's dispalyName as the Inbound SR is configured to be. Regards.

So it is working as expected right now?Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

Hi Paul, it's correct, it's working as expected. The key thing is to understand well the concept of the Reference attribute. Thanks.

Hi, i still would want to understand better how this ReferenceDN mapping works. In my first test, i worked with a table like this one: ID_USR ManagerID DisplayName CO195215624 CO95215624 Guajardo Lopez Jesus CO95215624 CO195215624 Ferrusquia Salgado Fernando (Anchor attribute: ID_USR) At my Inbound Synchronization rule, i selected to mapping the "ManagerID" (from the table) to the "manager" attribute (at metaverse). After Full Import and Synch, i got to see the user "Ferrusquia Salgado Fernando" with the value "Guajardo Lopez Jesus" as his manager (blue linked). Now if i'm working with a table like this: ID_USR ManagerID Position DisplayName CostCenter EmployeeType CO195215624 CO95215624 CIO Guajardo Lopez Jesus 1234 FTE CO95215624 CO195215624 Consultant Ferrusquia Salgado Fernando 1234 Student What i want to know is how in the first table, the Reference DN (that pointed out to the ID_USR) took the DisplayName value? (i didn't defined to take it that way), and how it's supposed to work with the second table with 6 columns (will DisplayName be taken again automatically or which attribute will be?). Thanks.

FIM Sync will display the value that is set in the attribute displayName, if you flow other information within the metaverse for this attribute (or leave it empty) other information is shown.Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!