Hi there,

I am facing with a trouble .. seem so strange.

I'm trying to sync user from CSV file to AD so I create 02 MA

1. MA connect to CSV (MA-CSV)

2. MA connect to AD (MA-AD)

After running "delta import and delta sync" on MA-CSV, it's trigged to Outbound sync and can Export MA-AD to create user on AD.

I change one attribute on CSV  file and run "delta import and delta sync" again. It is also trigged Outbound Sync and after that, run Export of MA-AD and I can see the update on Connector space of MA-AD without any problems. However, it is so strange that AD user is not updated !

But since the second update, it works perfectly. So I always miss the first one.

I did try to change "delta import and delta sync" ==> "delta import and Full sync" and it is okay with update for the first time.

But I cannot find the root cause here.. anyone can explain for me please?

I believe that AD is working okay (nothing related to replication issue on AD because I just have one AD)

Thanks a lot.

This does not make sense.  The purpose of a sync, delta or full, is to produce the pending export. Since a delta sync did create a pending export, the change to a full export should not have made any difference. I believe you are misrepresenting the issue somehow.  Try to show some examples, screenshots or something that proves your claim.

Thanks for your reply.

I did also believe it should be "a bug" from MS since cannot find any reasons for this.. and instead of using full sync I just use import back from AD to connector space (staging only) before running export and it can update for the first time. It is a "solution" now..

It is so hard to believe but I am sure it is.

I just support remotely something related to FIM and now it works with the "solution" above and it is temporary acceptable

However, once I have time, I will try to build a small DLL for you to test this case.

Duc,

Did you check the order of precedence? Do you have equal precedence? 

It is not equal precedence now, but I think it is not a problem..?

I have two Data sources for One Metaverse object but each entry is different.. two data source object entries cannot sync to the same entry in metaverse.

You are not exactly correct on your assumptions.

Please assess the Precedence Issue.