Problem with metaverse attribute flow precedence
I created a text file MA with some attributes (ID, FIRST_NAME, LAST_NAME) and a FIM Ma. Then I configured an inbound synch rule, where I concatenate first and last name to create a display name: FIRST_NAME + " " + LAST_NAME -> displayName I would like to configure the precedence of the displayName attribute in the metaverse designer so that the text file MA has an higher precedence, but when I try to do it, I get this error message: "A synchronization rule contributed flow may not have a higher precedence than a Synchronization Service Manager defined flow." As a result, the new users created in the FIM portal show "(No display name)". I noticed that now the "Publishing Active Directory Users From Two Authoritative Data Sources " document states that the attribute precedence should be configured selecting the "use equal precedence" checkbox, while previously it stated the the HR MA should be made prioritary. Is this something that changed from RC0? Does the error I received mean that now it is possible to configure "normally" the precedence (i.e. without checking the "equal precedence" box) only for attributes that make no use of custom expressions? Thanks, PaoloPaolo Tedesco - http://espace.cern.ch/idm
October 28th, 2009 6:13pm

Yes, this has been changed and will be fixed by RTM.For now, you will have to use equal precedence.Sorry for the inconvenience....Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2009 8:28pm

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

Other recent topics Other recent topics