Hi , I have a requirement that , i have to pass the reference attribute(manager), from metaverse to the FIM Portal. But when i try exporting the users to FIM, all other attributes except manager attribute is exported. Can anyone help me out in this as early as possible as we have an urgent requirement. Thanks in Advance

This sounds to be a precedence issue ... are you flowing manager back in from the FIM Portal? If so you will need to turn on the EQUAL PRECEDENCE checkbox for the manager attribute of the metaverse group object. Unfortunately there doesn't seem to be a way around this ... normal precedence doesn't work if you want subsequent changes in the FIM portal to flow back into the metaverse. I presume you've got the MANAGER attribute specified as a direct import and export flow for the FIM MA for your group object?Bob Bradley, www.unifysolutions.net (FIMBob?)

We export the User datas from HRMA to FIM with manager attribute.we created a manager attribute in Person object in metaverse and then we mapped the value to manager attribute in person object in FIM MA.but still we are facing the issue. How to proceed in that case.

Just follow Bob's advice - check your precedence configuration. The easiest way to debug an issue like this is using the preview feature. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Just to chime in on something UNIFYBob said above.......attribute precedence did not work properly but there is hotfix available from MS PSS for this that fixes this problem. After hotfix is installed and you run full sync on MA that is authoritative for this attribute, attribute precedence should work as expected, even if you don't use equal precedence.

When you exporting objects from the FIM Sync-Engine to the FIM portal, do you see the manager reference in the pending export object? You say, the attribute is not exported. Are there any error messages in the export run profile? /Matthias/Matthias

I'm having the same problem that is being indicated above. The difference is that I'm not pulling Manager back in from the Portal so the need for equal precedence is not there. Here is the error that I am receiving: dn-attributes-failure That is about all i have to offer. I am not getting a Stack error so I'm somewhat at a loss. If i remove Manager from the MA Mapping then all is well of course. Thanks