I have an inbound synchronization to FIM from a HR database, If the phonenumber once have been populated, then if I delete the phonenumber it will not delete it from FIM. Nothing happens when I synchronize. The HR database have precedence for the attribute and the FIM MA allows NULL for export to the field. The CS for the HR databse shows that the attribute has been removed, but MV object keeps the old value, and then says that FIm is the contributing MA. Any ideas why?

Do you also have an inbound attribute flow from the FIM MA to the Metaverse that is a lower precedence than the inbound flow from HR? If so, then the FIM MA will contribute the attribute flow to the metaverse when the attribute is removed from HR. I'm pretty sure that is the behavior you are seeing. -Jeremy

Do you also have an inbound attribute flow from the FIM MA to the Metaverse that is a lower precedence than the inbound flow from HR? Jeremy, is this a typo? Shouldn't this read higher? Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

No typo. I think he has: HR->MV - Precedence 1 FIM MA ->MV - Precedence 2 So, when he deletes the value from HR, it is being contributed to the MV by the FIM MA. What he wants to have happen is have the value deleted in the MV and in the FIM MA when it is deleted in HR. So, the solution is to remove the inbound flow from FIM MA -> MV. -Jeremy

Of course. Bad configuration from my side. Thanks!