User15825734199907344521 (Customer) asked a question.
I am having an issue with updating a custom attribute called "manager". This attribute is mapped from a directory integration from Active Directory to OKTA. It is only mapped on create so it is possible that some users did not have this value set when it was imported into OKTA. The results of this are evident when you run a get on 2 different users (the first that had the manager field imported from AD and 2nd that did not):
@{ manager=; managerId=}
@{managerId=}
By contrast the managerId attribute is also a custom attribute but it is not mapped to anything. Every user seems to have this placeholder and even if it is blank can be updated via the Rest API.
Is there a way to "force" the attribute to be created if it does not yet exist in the user's profile via the API? If not, is there a way to update the import process so that it creates a "blank" attribute for the user?
Hi! So after an import, are you saying that in the user profile, the attribute is not listed? But managerId is listed, but blank? Thanks for the clarity!
If there was no value in Active Directory at the time of import the manager attribute did not get created so the update via my script fails. On attributes that were not set to import however they appear to have been created automatically in the profile and update fine.