According to the documentation, FIM is supposed to call the ExportEntry method of my IMAExtensibleCallExport interface to be triggered, with a "delete" modifciation type. This is not happening. During outbound sync, the metaverse object is being deleted, and the Extensible MA connector space has delete pending exports. Then, during Export of the Extensible MA, the pending exports are removed. And objects of type "placeholder" appear instead. And no delete modification type is passed to the ExportEntry method. Are the placeholder objects normal, or is it a clue as to why ExportEntry is not being called? My Extensible MA's deprovisioning rule is set to "Stage a delete on the object for the next export run ” I've read Markus' deletion documentation... http://social.technet.microsoft.com/Forums/en-US/identitylifecyclemanager/thread/603c4f8c-d782-4625-a045-009d15ed0f3b ...and it's getting as far as the last step before the summary (Extract from Markus' doc..."During the next export run, ILM applies the staged deletion to Britta’s representation in the connected data source CDS2, which also deletes her connector space object in CS2.").

OK, so the symptom of "placeholder" objects with no delete modification types passed to ExportEntry would appear to be due to the lack of a confirming import. Is it intuitive, that the ExportEntry method will be called during the confirming import? Or will it be called during the sync step of the confirming import? I'll attempt to implement Sebastien's proposal described in this thread, to produce an AVP file during my export... http://social.technet.microsoft.com/forums/en-US/identitylifecyclemanager/thread/024ad6f3-3025-40ce-88f0-3c572bf5990f/

As already mentioned in your other post, I belief, you are dealing with a configuration issue of your ECMA. There are two export types, call-based and file-based. Make sure that you have the ECMA configured correctly and that an Add comes through. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation