![]() ![]() I hadn’t shown how to bundle the work that was done in the Web UI into a deployable content type via a WSP package. Historically, the problem with using Word documents has been that the techniques outlined in the whitepaper was only shown through the UI. It’s easier to teach end users one (or two) new things about Word documents and get forms than trying to push them into a new forms technology. However, there are a ton of forms, like vacation requests, which don’t need the one-to-many relationships that InfoPath would provide. ![]() Forms like expense forms are much better in InfoPath than Word. InfoPath is much more powerful and is essential when you need a one-to-many relationship in the data. It’s assumed that you can copy properties to SharePoint and back. The final reason is because most folks know that InfoPath is SUPPOSED to handle data. Either it’s not installed, licensed, or it’s not licensed for Forms Services on SharePoint. However, the other reality is that not everyone can use InfoPath. There are a few reasons, not the least of which are the issues with getting InfoPath to play nice with my content types on SharePoint. I’m often asked why I’m not talking about InfoPath. The net-net is that this is a quick way to convert a paper form put together in Word into a “smart form” that can be used online. Take a look at the following which has four QuickParts on it. When the user isn’t hovering over the content, you can’t even tell that the text isn’t just normal text in the document. When a user enters information into the document, the information is copied into the properties by Word. For those of you that haven’t seen it, a quick part in Word sits on the surface of the document. I’ve talked about the general principles in the whitepaper I wrote for Microsoft “ Managing Enterprise Metadata with Content Types.” That whitepaper is focused on understanding how SharePoint’s search features can be activated for use with the metadata that users enter - and it walks you through a step-by-step process for creating a word document that uses quick parts to enter metadata. For a few years now, I’ve been talking about a technique that everyone can leverage to get metadata into SharePoint - without the users having to do something different than they normally would. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |