SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got errors using more complex SharePoint fields like enterprise keywords, managed metadata or custom fields that contain code with InfoPath and Workspace clients. Is this really not supported? Is there any workaround, e.g. treat as basic string field or whatever?

There must be something...otherwise this would mean, items with metadata tags cannot be managed with InfoPath and cannot be offline with Workspace. ????

share|improve this question

Yes, this is correct. InfoPath really doesn't support managed metadata.

The Managed Metadata field is such a good idea (don't start me on the implementation, though) that lots of people want to use it - but it's unusable with InfoPath. Crazy.

Still, at least Microsoft are aware of the issue.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.