When a Forefront Identity Manager Synchronization Service (FIM Synchronization Service) database (metaverse) attribute has more than one import flow from one or more management agents, you can use attribute precedence to define the value that flows when you set the value of the attribute in the metaverse. A special form of attribute precedence is the manual precedence. Manual precedence gives you additional control to decide what attributes and their values contribute to the attribute in the metaverse in case of multiple import flows.
The following are examples of manual precedence in a rules extension:
- Handling multiple connector space objects to
the same metaverse object
You can accumulate attributes from multiple connector space objects in the same management agent to a single metaverse object with manual precedence. For an example, see How to: Handle Many Connector Space Objects to One Metaverse Object in the Same Management Agent.
- You can merge multiple attributes from the
same management agent with manual precedence. For an example, see
How to: Merge
Multiple Attributes from the Same Management Agent.
- Using the Last Contributing Management
agent
You can specify that the value of an attribute is changed only if a specified management agent made the attribute value change. A value that is contributed by another management agent does not change the attribute value. For an example, see How to: Modify Attribute Values Using the Last Contributing Management Agent.
- Using the
LastContributionTime property
You can specify that an attribute is set in the metaverse only if the incoming attribute was modified at a later time in the connected data source.
- You can handle attribute value accumulation
using manual precedence. For an example, see How to: Handle Attribute
Value Accumulation.