Direct mapping of custom user attribute won't sync resources in FIM 2010
I've created a custom attribute named calculatedDistinguishedName as an Indexed String in FIM 2010 RTM portal and did all the bindings to get it connected to the user resource type. As the intention of it is to update an ActiveDirectory entry with this attribute's contents, I also created an extra attribute called calculatedDistinguishedName in Metaverse Designer and configured the attribute flow to have it updated from FIM MA. I don't know if this is relevant but calculatedDistinguishedName attrib is calculated via a custom C# workflow that runs in FIM and its data flows correctly from FIM to Metaverse. When it gets to sync out to ActiveDirectory, using a direct mapping nothing happens. Other attributes in the same syncrule flow out properly. calculatedDistinguishedName => dn The interesting part of this story is that if I change the mapping to use a custom expression like the code below, synchronization works as it should, the attribute flows out to ActiveDirectory and set the user to the expected OU. CustomExpression("" + calculatedDistinguishedName) => dn Does anyone know what could be wrong here?Carlos Cardoso - Programmer's Informatica
May 6th, 2010 11:56pm

Don't know if it is related but I have the same thing happening with homeMDB (also a reference attribute in AD)!Anu
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2010 12:50am

Carlos, We ran into similar issues in the past. It seems that you cannot do a direct mapping between a string attribute and a reference attribute. Having said that, you can map a string directly to a referenced attributes but you cannot map a variable of type string to a referenced attribute. I do not know if this issue was corrected in the latest update but we found two workarounds. The first you have which is simply using a custom expression such as the one indicated in your post: “CustomExpression("" + calculatedDistinguishedName) => dn” And the other is to address the mapping from the FIM Service MA attribute flow (the old fashion way). Hope that helps Issam Andoni http://www.zevainc.com/andoni
May 7th, 2010 3:32am

Issam, This is not a blocking issue since I got it working this way but it just didn't feel right. All I can imagine from this scenario is that CustomExpression returns something that is not a raw string and that FIM Sync Service internals is able to parse and cast to the correct target type, be it either a regular or reference attribute. Thanks for the clarification and the extra workaround.Carlos Cardoso - Programmer's Informatica
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2010 3:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics