Ever got this helpful message when trying to configure the user profile to use a termset?
There was a problem retrieving data for this field. Updating values in this field is disabled temporarily. You can still update values in other fields.
There are lots of potential causes for this. Earlier today I found that my problem was caused by an issue outlined on Donal Colon’s blog.
Here’s my setup:
- Managed metadata started, configured and running as the only MM Service in my farm
- MM service was associated with all web apps
- User profile service was configured correctly (I could do profile syncing) and could even associate fields with a Managed Metadata term.
However, with all these things, I wasn’t feeling any User Profile / Managed Metadata love. This was potentially a big problem as I have a client delivery counting on User Contexts in Search (depending upon said UP/MM love).
Enter Donal Colon.
His post suggests that if you don’t tick the default storage location for keywords when you have TWO MM services then you can get problems like the one I encountered. He also highlighted that having two MM services conflicting can cause a problem.
Well, I only had one Managed Metadata service, but if you don’t have this box ticked, then you aren’t getting any terms in your User Profile Service either.