As far as I know, everytime you perform a crawl on the
User Profile Service Application certain
Active Directory fields are converter or added (if already exist) to the
People term-set. We found a quirk that I'd like to know if we could work around.
User Profile Service Application added a term set called
Department and added terms based on the
Department field of our users in AD. However, if we change the name of a department in Active Directory the existing term doesn't get updated; a new one gets created.
To give a simple example, the
User Profile Service Application will pull in
Human Resources as a term for the
Department set in the
People super-set. Say we have all our new hire documents tagged as
Human Resources, but a mandate comes in saying that we need to shorten the Department name to
HR. So we do that, and the
User Profile Service Application creates a new term, but all our
HR documents are now incorrectly configured for search.
Does anyone know if there is a way to configure the
User Profile Service Application in such a way that if an option changes in Active Directory (say we change Human Resources to HR) that instead of creating a new term altogether it would update the existing term?