Hi, Take a scenario where there are many different systems, with data in them already (HR, AD, Oracle, SQL) etc - and then we stick FIM into the mix. Is there a seeting in FIM that basically says: leave the current data as is, and only start using your Sync rules, MPRs etc on any new data introduced into the system? Hope my question makes sense. Thank you

Hi There, I don't think this is true. Your data within the synchronization engine can be modified as much as you like when you introduce the new rules into the environment. Same as if you changed the synchronization rules for the user object going to HR classically, adding a declarative synchronization rule would to the same thing. Inbound declarative synchronization rules would apply immediately to any of the objects in the connector space to which the scope and relationship criteria have successfully applied therefore changing how data may be imported (unless there is an associated classic rule which would override it based on the premise of classic rules winning). Your existing objects can be affected by outbound MPRs simply by using a "transition in" MPR with a workflow assigning the attribute flow which is checked to "Update on Policy Changes". This would apply it to all the objects that are in the set you've already defined. If you do not have the "Update on Policy Changes" selected when you create the workflow then the outbound rules would not be applied to the existing objects in the environment (if they were already exported into the portal). Hope this helps. B

hi there, I’m not aware of an out-of-the-box functionality that doesn't touch initial-load data. However, due to the extensibility capability there might be some options to achieve this approach, e.g. Set up a new FIM attribute "LoadDate" and bind to all objects you want to manage with FIM Import the objects from your sources with attributes as needed + the additional static attribute that stores the current load date/time Customize all your outbound rules & MPR, etc. to be executed only if the LoadDate > date/time of your initial load. However, from a general perspective I'd double-check, if I really want to deploy such scenario, since it could be very complex to manage Hope this helps Matthias /Matthias