This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Virtual mapping attribute (object reference) not provisioned in AdHoc

Hello,

for ADS synchronization, I have created a custom virtual attribute of type 'object reference'. This attribute contains the short name of the account owner's department (UID_Person.UID_Department.ShortName). The field 'Department' is used for a certain depth of the org tree, while this custom field (division in AD) is used for the Department object to which the Person is directly assigned.

When running a full provisioning of the project, the values are written to AD correctly. However, if the Person moves to another Department, the Department field is updated correctly (updated by a template), while the division field is not overwritten.

Do object references not get evaluated in AdHoc provisioning? Can I somehow force the evaluation? Or do I need to create a custom attribute to the ADSAccount table and map that to division?

Best regards,
Christian