InfoPath ideas not to lose
I gave a presentation on InfoPath and InfoPath Forms Services to the SharePoint Users Group in Manhattan last month. Here are a few ideas I got from the questions people asked. I recently found these written on some scrap paper in my bag and figured I'd publish them so I wouldn't lose them. I've done absolutely no research on these, so solutions may already exist...
- If I have a large number of form templates, I don't want to put them all under the New button in a single library. In fact, in a publishing site I probably don't want to have users able to see the library at all if the site is a heavily customized publishing site. I need to create a control which gives me the ability to run the same JavaScript that the New button does, but lets me configure the template to use. This should be some simple JavaScript to emit and the control should be light weight and output something to the user which can be stylized via CSS
- If I've got a form that gets newed up from one form library but the content gets saved to another form library, I've heard that there are lots of people out there struggling with permissions. The destination library has restrictive permissions. The source library has wide open permissions. A user with a relatively low level of permissions creates a new form based on a template from the source library but doesn't have permission to submit the result to the destination library (see - this is why you should never test as while logged in as an Admin user). The solution most likely involves impersonation, but how do you do that in the tool? InfoPath is supposed to be a PowerUser tool, not a developer-required tool. Maybe this addin code could be created and placed on CodePlex or something.