Hi there, please excuse my simplification of the situation here and I apologise if I don't provide enough useful information, but I'm learning FIM as I go. I have a development background, not an identity-management one. We have a custom MA already which is used for exporting data to a crm system via a web-service. We are trying to perform a data-migration proof-of-concept task where we do a one-time import of data from this web-service using the existing MA for both import as well as export (I couldn't find a way to copy the MA and turn it into an import-only one). I've followed this article, but by modifying our current export ma instead of creating a new one: http://www.wapshere.com/missmiis/fim-walkthroughs-import-data-from-hr-to-the-fim-portal When I run the custom MA now, I get the data into the MV and can see this when I query the MV, but data doesn't go out to FIM, even when doing a full sync with import on the FIM MA. This is what I see on the custom MA history: I'm expecting 10 objects to go into FIM... BUt there are hundreds of other objects I'm not ready to import just yet coming across in the MA (we are using DSML)... Inbound Synchronization Projections: 0 Joins: 0 Filtered Disconnectors: 0 Disconnectors: 168 Connectors with Flow Updates: 0 Connectors without Flow Updates: 10 Filtered Connectors: 0 Deleted Connectors: 0 Metaverse Object Deletes: 0 Outbound Synchronization - FIM Service MA: Export Attribute Flow: 10 Provisioning Adds: 10 Provisioning Disconnects: 10 From what I can understand of it, the provisioning disconnects are the indicator that it's trying to get the data into FIM but failing somewhere along the line. I suspect it's something to do with a primary key (or the FIM equivalent) not being sync'd across all objects properly and so objects are being dropped. Can anyone help shed any light on this for me please?

You need to configure an inbound synchronization rule. For more details see: Understanding Data Synchronization with External Systems Introduction to Inbound Synchronization Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hello Markus, thank-you. I have configured a sync rule to be inbound and outbound already and as part of that defined the inbound attribute flow, taking care to include our joining attribute in there. Is it better to have two sync rules? One for Export and one for Import? We had this Export one setup already and I altered it to be bi-directional, but nothing goes into FIM from the Sync Engine.

Did you run the export run profile? You can get the provisioning disconnects if you have run a synchronization (with provisoning enabled) without first running the export. In your case, FIM has provisioned 10 objects into the FIM Service MA connector space. If you do not export, and run the sync again, FIM first removes the provisioned objects (provisioning disconnects) and will reprovision the objects (provisioning adds). HTH, PeterPeter Geelen - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

I have configured a sync rule to be inbound and outbound already and as part of that defined the inbound attribute flow, taking care to include our joining attribute in there. In this case, you should use the introduction to inbound synchronization as template. The doc has all required steps to get something into FIM. It can be as simple as provisiong not enabled... Two or a combined SR is subject of your personal preference. I like separate SRs better because I think it makes it simpler to read a scenario. However, this is just my personal opinion... Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thank you Peter, that helped! It was just the order of the run profiles! Data is moving now, and I'm left with some validation errors, which I hope will be simple enough to resolve, i.e. <RepresentationFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <AttributeRepresentationFailure> <AttributeType>validFrom</AttributeType> <AttributeValue></AttributeValue> <FailureMessage>An attribute is required to complete the operation.</FailureMessage> <AttributeFailureCode>RequiredValueIsMissing</AttributeFailureCode> </AttributeRepresentationFailure> </RepresentationFailures> Though making this attribute optional in the Portal/Schema Management interface doesn't seem to have an effect, even after restarting all services. I need to do some more reading I think :)

Are you synchronizing groups? You can find more details about the required attributes for users and groups in the How Do I Guides. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

No, this is data from a CRM application we import/export via a custom MA we've had developed for us.