First published on MSDN on Feb 12, 2016 Update 6/23/2017 (working on Code formatting for presentation) In this post we will focus on the following section of the Management Agent Rules Extension.
In the Synchronization Service click on the MA that you wish to map the Attribute Flows to the above Code. In this example we were mapping the accountExpires attribute from an object in the Connector Space to an object in the Metaverse converting the value from an integer value to its String equivalent. Lets take a look at a User Object in Active Directory who has the accountExpires attribute set.
this is what it looks like in the ADUC GUI but if we look at the actual value in ADSI Edit or on the Attribute Editor Tab of the Object in ADUC
so the actual value within AD is 131026644000000000 When syncing this Value with the FIM / MIM Portal which needs this attribute to be converted to its Date Time Format we use this MapAttributesForImport post as an example to achieve this task. ## Additional information on "IMASynchronization.MapAttributesForImport Method" can be located here
In the following post I detailed 2 Way Account Expires Rules Extension , which utilized the "IMASynchronization.MapAttributesForImport Method" but also focused on the importance of equal precedence and the "IMASynchronization.MapAttributesForExport" method. In this post we will focus on the actual "IMASynchronization.MapAttributesForImportmethod as opposed to an individual function such as accountExpires to employeeEndDate.
Now lets look deeper into MapAttributesForImport, the following code snippet includes helper functions which we will point out in the follow up post. For this post we will focus on only the section that is used to Map Attributes for Import or more accurately said the “IMASynchronization.MapAttributesForImport” method , the goal is to provide some explanation of how to build your Custom MA Extension one method at a time.
After you have you code compiled for all attribute flows that will call one of the functions in this method be sure to select the flow direction of Import and use the case when setting the Flow rule name: which is within the Advanced mapping type See Management Agent Advanced Attribute Flows Post. Additionally be sure to select all attributes from the Data Source that the function uses to build the value for the Metaverse attribute.
Questions? Comments? Love FIM/MIM so much you can’t even stand it?