Hy, Is it possible to insert two conditions in or in relationship Criteria of a Synch Rule? Thanks a lot. Regards. Luka.

in portal the conditions is the relationship are only "And". however you can configure multiple "Or" join rules using the classic method in the Synchronization Manager and you can even use rule extension to resolve joins. go to your Management Agent -> Properties -> Configure Join and Projection rules, then create multiple join rules It's never too late in life ... to start living

There are no Dummy questions!!! Amer is correct, simply click "Add Condition" to get more "Anded" conditions but you could also have more than one inbound sync rule with different relationship criterias and the lower the value for precedence is the earlier the sync rule will be applied. //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego

Ok as an example. I import some user first time from DB and AD.They join on an attribute we call ID (but its valid only for first load). Then this user will be created on portal and a custom activity calculate an uniqueID which will be exported to AD. Now my provisionig rule towords AD try to join on unique id but this happens: 1)Import DB 2)Import AD (Join) 3)Export to FIM (calculate unique ID but also SR not match for join with unique id (becouse it has been just calculate)) 4)Import to metaverse (import unique id and provisioning SR) 5)Export to AD fail, try to create duplicate object :( Any idea? Thx a lot. Luka.

There are no Dummy questions!!! Amer is correct, simply click "Add Condition" to get more "Anded" conditions but you could also have more than one inbound sync rule with different relationship criterias and the lower the value for precedence is the earlier the sync rule will be applied. //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego

the best approach is to have one shared attribute between your DB and AD, why not generating this uniqueid in DB, and have AD join based on that. if you are stuck with the current methodology, you can fix the join by disable "synchronization rule provisioning" in the synchronization manager, and import the uniqueids into the metaverse then run full sync on AD MA to join the users based on that attribute, after that you can re-enable the SR provisioning.It's never too late in life ... to start living

Yes already do that. I agree with you that unique id is the goal but datasource are external and we do the trick for first load. Yes I disable Synch rule prov and then re-enable. Anyway or condition could resolve my problem very easy :) Thanks a lot. Regards. Luka.