Hi, I have an attribute that is multi-valued in FIM and can have none or many values. I export this information to a custom attribute in Active Directory using the AD MA, and to another external source using an Extensible MA, all my provisioning is done by classic coded provisioning. When the last value of the attribute is removed in FIM this is imported okay, and the attribute is removed from the metaverse object on synchronization as expected. The sync also informs the AD MA of the change and I get an attribute flow to AD. The problem though is that for my Extensible MA I don't get any attribute flow even though the CS object for the XMA has one value for the attribute and the MV object has no attribute because it has been removed. I wondered if this was to do with not doing a confirming import, so I've written that and still have the problem. I've also tried forcing it in provisioning code to always write the attribute no matter what (making it blank in the XMA CS so that at least it knows about it), but I just get that the attribute is read-only even when I remove the attribute flow in the XMA. I'm totally stumped on how to get this work, can anyone offer any help? Thanks, Martin

Of course, now I realised having assumed it was a complex problem that I'd forgotten to mark the attribute in the MA as Allow Nulls, so of course it couldn't be removed because it broke that rule. Added Allow Nulls and its all fine and dandy. In the words of Homer Simpson, d'oh!