I've discovered an odd (to me) anomaly with our MAD connector. The
driver contains a schema matching policy that maps "Employee ID" in the
ID vault to "employeeID" in Active Directory. If I populate Employee ID
for an existing user, the attribute gets passed to AD normally. If this
attribute is populated during user creation, whether from an LDAP import
or via our PeopleSoft-to-SQL-to-vault (don't ask) connector that
automates account creation, the driver refuses to create the AD object
with an 'attribute conversion operation' error. It seems that the
schema mapping functions only on a modify operation, not on a create.
Why would that be?

(IDM 4.02 & eDirectory connected to AD 2008R2).