Hi,We have applied update 3 on different environment and all four with different resultsEnvironment 1 (DEV-Customer):Before Update 3: FIM 2010 RC1 Update2 with data and configAfter Update 3: same as before and in addition broken RCDCs (when viewing objects in Create/Edit/View mode) for Sync RulesEnvironment 2 (VM-DEV-Personal 1):Before import: FIM 2010 RC1 Update3 fresh installed with NO data and NO configAfter import: broken RCDCs (when viewing objects in Create/Edit mode) for Sync Rules. When in View mode no issuesEnvironment 3 (VM-DEV-Personal 2):Before Update 3: FIM 2010 RC1 Update2 with data and configAfter Update 3: same as before and in addition NO broken RCDCs for Sync Rules(PS.: this environment delivered the export for Env 2)Environment 4 (TEST):Before Update 3: FIM 2010 RC1 Update2 with NO data and NO configAfter Update 3: same as before and in addition NO broken NO RCDCs for Sync RulesTo resolve this we tried the following:* RCDCs for Sync Rules from an environment that was still on Update 2 were imported in the Update 3 environment, but no changes are detected and imported* We stripped down the create RCDC and after that loaded the RCDC into FIM after adding a TAB. When trying to create a Sync Rule the PARAMETER tab was not shown while it was added. The TABs to the left of the PARAMETERS tab were shown with no errors. As soon as we added the TABS for Inbound and Outbound Flow the RCDC started to show errors ("there's an error in the SynchronizationRule display configuration. Please contact your system administrator")Looking at the scenarios specified above, at this point we believe the RCDC configs are correct (we did not adjust those for Sync Rule Objects) and nothing is wrong with those. We also believe there is something wrong with the underlying config/data/whateverAnyone seen this?Cheers,JorgeJorge de Almeida Pinto [MVP-DS / AD DS TechNet Forums Moderator] [Sr. Technical Consultant @ Oxford Computer Group] (http://blogs.dirteam.com/blogs/jorge/default.aspx) (http://www.oxfordcomputergroup.com/)

Please file a bug on connect to get the issue tracked.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation