When I run a Full Sync on the AD MA, I get a bunch of "ambiguous-import-flow-from-multiple-connectors" errors when running AD MA. How can I find out which attribute is causing this?

If I open one of the errors and run a "generate preview" I can see there is a join ("match") based on (data asource attribute) samaccountname &  (metaverse attribute)  accountName but I don't seem to be able to figure out what attribute is causing this and / or needs precedence.

Anyone any ideas?

JD

Hello,

this error occurs because you have more than one CS object linked to one MV object.

In this case FIM can not resolv the precedence of Attribute flows correctly, because they have all the same precedence. Or regarding to your question, all Import attibutes flows are causing the Problem.

You have to configure Manual precedence with advanced Attribute flows in this case.

or

If multiple CS objects to one MV object is not was you Need, get rid of the second (or more) connector from that data source.

See more here:

https://msdn.microsoft.com/en-us/library/windows/desktop/ms696034(v=vs.100).aspx

http://www.wapshere.com/missmiis/overcoming-multiple-personality-disorder-in-the-source-data

-Peter

Thanks Peter. Is there a way to find out which attribute is causing this?

JD

As I said above, the whole second CS object is causing the problem, (so all Import Attribute flows).

Or if the second connector to MV is a mistake then the "join Attribute" is causing the problem, you have to objects with same value in CS.

-Peter

Thanks - will give that a go tomorrow.

JD