Difference between equal precedence and disabled/unchecked manual precedence in FIM. RRS feed

  • Question

  • I have an attribute say ABC in MV for which two source contribute XYZ,MNO respectively.They are direct mappings.
    I have set the precedence to XYZ in MV designer to order no 1 and then MNO.When I updated the value of attribute corresponding to ABC from MNO ,the value flowed to MV.
    I expect this value from MNO not to flow as XYZ is having more precedent.Again when I change the attribute corresponding to ABC from XYZ that is getting updated.
    This means the last writer wins.

    Isn't it the same as Equal precedence?If no where am I going wrong?
    Tuesday, June 18, 2013 11:39 AM


  • Per your example, as long as there is no value yet in the metaverse, MNO is able to contribute an initial value.

    Per TechNet:

      • As long as the metaverse attribute has not been populated yet, all MAs that have an inbound attribute flow mapping for the attribute configured can flow a value.
      • As soon as the metaverse attribute has a value, the value can only be updated by a management agent that has the same or a higher precedence as the last contributor.
      • If a management agent with a lower precedence than the last contributor tries to flow an attribute value, the flow is rejected.

    For more information, see the following article, towards the bottom, under the heading "Attribute Flow Precedence":

    Regards, Jose Garza | MCP, MCSA:2003 |

    Tuesday, June 18, 2013 6:13 PM