I had the great honor of presenting at my first SharePoint Saturday @ New Hampshire on Saturday, September 2, 2012. Thanks to the NH crew for all the hard work. My topic was a comparison of using InfoPath with a list or a library.
The slides from my talk are located here.
The summary of my talk:
I discussed the pros and cons of list InfoPath forms (what I like to call "InfoPath lite" vs forms libraries. The considerations:
- Data connections
- List forms come with a data connection: the list.
- Data connections tend to trip the casual user up. So keep it simple.
- More complex data connections should lead the user to a form-library.
- Need for Repeating Content
- Repeating tables/sections are not available in a list InfoPath form.
- Following the KISS principle.
It's important to take the time to make sure you have a robust process in place prior to looking towards SharePoint or InfoPath to provide a solution. Pre-work is vital. I compared this project stage to preparing to cook a meal using a wok. In wok cooking, the cook must cut/measure/prepare everything before the start of cooking. The actual cooking itself is quick and efficient. Preparing for any SharePoint/InfoPath implementation is a lot like cooking with a wok. (What made this analogy even more appropriate was the room I presented in was a college cooking demonstration room: think Rachel Ray/Martha Stewart set. If you want the Duck recipe I shared at the beginning, just ask!).
Conditional content simplifies the form and multiple pages prevent scrolling: remember, people HATE to scroll.
So what are you doing to make the end user's work life easier via InfoPath?
Congratulations, your blog is appealing and informative. Going through your Information, I found quite a few new ideas to implement ... Thanks
ReplyDelete