We are having an issue where our attributes precedence seems to not work properly. Our display attribute is set so that AD has the higher priority than my other MAs including FIM. The problem is that all those records that are initially getting created end up with the displayName field empty. I was under the understanding that if some other MA actually had a value it would get updated. Is there a way to allow this to happen in those cases.

You are correct, on the inbound side (from a connector space to the MV), a MA with the same or a better precedence value than the last metaverse contributor can flow a value to the metaverse. However, on the outbound side (from the metaverse to the connector space), a value can only flow if it was contributed by a MA with the same or a higher precedence than the target. From your description, it is not clear, what part fails. Based on your description, if you don't have a displayName field populated on an AD DS object, it will not be populated by FIM... Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation