Is anyone seeing an issue where if you are using Sync Rules to provision/flow attributes, the corresponding advanced export rules on the MA don't fire during a delta sync? If I run a Full Sync on the MA/preview on the object then the advanced export rules do fire. I've got build 3561 going here.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

I have the same build, and a similar problem with rules not firing on delta sync, but a different scenario ... in my case I had equal precedence set on a "pwdLastSet" attribute which should have set up an export to the FIM portal when it was updated in AD. In my case a delta sync preview did nothing, but a full sync preview gave the expected result. I figured I could find a different way to meet my requirements, and I did ... but I still believe that this is a bug.Bob Bradley, www.unifysolutions.net (FIMBob?)

I have the same build, and a similar problem with rules not firing on delta sync, but a different scenario ... in my case I had equal precedence set on a "pwdLastSet" attribute which should have set up an export to the FIM portal when it was updated in AD. In my case a delta sync preview did nothing, but a full sync preview gave the expected result. I figured I could find a different way to meet my requirements, and I did ... but I still believe that this is a bug.Bob Bradley, www.unifysolutions.net (FIMBob?)

Just be a bit careful with this specific scenario - there was an issue in conjunction with equal precedence that has been resolved by a hotfix that is available. From a high-level perspective, the full sync scenario doesn't help since EAFs are "brute force" applied in case of a full sync... So, from a problem description perspective "full sync does it and delta sync doesn't" doesn't really help - if you can see what I'm trying to get at. The focus should remain on the delta sync and why an expected state is not reached. You might be a victim of the case that is addressed by the hotfix though. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Just be a bit careful with this specific scenario - there was an issue in conjunction with equal precedence that has been resolved by a hotfix that is available. From a high-level perspective, the full sync scenario doesn't help since EAFs are "brute force" applied in case of a full sync... So, from a problem description perspective "full sync does it and delta sync doesn't" doesn't really help - if you can see what I'm trying to get at. The focus should remain on the delta sync and why an expected state is not reached. You might be a victim of the case that is addressed by the hotfix though. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hi Markus- I'm not using equal precedence here. Here is the precise scenario: 1. Full Import/Delta sync from Flat File MA projects to FIM Portal 2. FIM Portal creates ERE to provision user in ADAM (delta import and delta sync runs) 3. Export to ADAM (followed by delta import and delta sync runs). If you inspect the user object exported to ADAM, you will find it has all the attributes from the Sync Rule in order, but, my three attributes I have defined via EAFs are not there. 4. Run a Full Sync on ADAM (or full sync preview on user) and my three EAFs fire and are exported to ADAM.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Hi Markus- I'm not using equal precedence here. Here is the precise scenario: 1. Full Import/Delta sync from Flat File MA projects to FIM Portal 2. FIM Portal creates ERE to provision user in ADAM (delta import and delta sync runs) 3. Export to ADAM (followed by delta import and delta sync runs). If you inspect the user object exported to ADAM, you will find it has all the attributes from the Sync Rule in order, but, my three attributes I have defined via EAFs are not there. 4. Run a Full Sync on ADAM (or full sync preview on user) and my three EAFs fire and are exported to ADAM.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Hey Guys, Same exact problem here. Were you able to resolve the issue? Thanks PaulPaul N Smith

Hey Guys, Same exact problem here. Were you able to resolve the issue? Thanks PaulPaul N Smith

Same issue. build 3606 Update 2. Anyone resolved?

Same issue. build 3606 Update 2. Anyone resolved?