I have configured FIM 2010 R2 with two MAs (FIM and AD).  FIM MA has attribute flows using the MA, AD MA has attribute flows via the Synchronization Rules.

I have created Synch rules for both AD users import and AD users export.  The attributes are more or less the same.

Under the metaverse designer, I have configured equal precedence for attributes.

The initial load was fine, FIM was populated with my AD users.  Changes in AD are replicated to FIM.  However, when I make changes in FIM, the changes are rolled back or overwritten by the metaverse at the next sync.  Basically, I only ever get queued exports to FIM and never any to AD.

I've probably overlooked something very simple but cannot put my finger on it.  Any suggestions welcome.

There do not appear to be any relevant errors in either the FIM or application event logs.

You seem to have an export flow in your FIM MA (from Metaverse to FIM Service & Portal) (because it gets owerwritten), but do you have an import flow flow that picks yours updates FIM Service & Portal to Metaverse?

Can you give an example attribute?

Hi Gaston, thankyou for your interest.  An example attribute is "jobtitle", you can see that it flows both ways and has equal precedence yet I never seem to get it to flow MV -> AD.

FIMMA:

ADMA:

MV Designer:

MV and AD user object properties:

Take the "preview" button for a spin... odds are the synchronization rule isn't applying due to the set/workflow/MPR triple.  There aren't a lot of other variables given that you've confirmed the right values are in the MV.

Hi Steve,

So I made a change in FIM Portal to job title, then ran Delta Import.  Upon preview of Delta Sync I see the following: "Not precedent"

Have you tried to do Full Sycnhronization?

Hi Gaston,

Same result, just about all attributes from FIM Portal -> AD are "Skipped: Not precedent".  There are a couple that are applied.

Hi,

As You have set Attribute  at equal precedence. So the metaverse will have value for the attribute from FIM or AD which ever MA's sync profile you will run at last. 

If you need these few attribute value updated into AD from FIM so you can set FIMMA precedence  higher thn ADMA.

"Skipped" issue comes if you have set the precedence lower for any attribute for that MA.

Thanks~

Giriraj Singh Bhamu