Browser Forms

Re: Can browser and client forms coexist in the same library?

burghthing — Mon, 23 Jan 2012 18:27:48 GMT

I just found this post, specifically the 2nd suggestion (create as content types with a separate doc library to store the templates, named differently for each version of the form). I think I'll try this...

Re: Can browser and client forms coexist in the same library?

burghthing — Mon, 23 Jan 2012 16:27:44 GMT

Thanks for the quick reply, Anson. Unfortunately, I don't think using the dropdown to select 'open in browse'r or 'open in InfoPath' will work. In that case, the library would still only have one InfoPath template associated with it. Whereas I need two templates associated with the same library.

Re: Can browser and client forms coexist in the same library?

Anson Hidajat — Fri, 20 Jan 2012 03:11:03 GMT

I don't believe there is a way to build logic into your form to tell it to open in the client or the browser depending on which case it is. There may be a code solution that I'm not aware of.

If you go into a document library and click on the dropdown for an InfoPath form, you will see two options: Edit in Browser and Edit in InfoPath. Is this something that may be useful to you?

Can browser and client forms coexist in the same library?

burghthing — Thu, 19 Jan 2012 20:00:08 GMT

I support an InfoPath form that is published to a SharePoint 2010 forms library. I want to turn it into a browser form and have any new requests open with that version, while existing requests open in the old client form. Do you know if there is a way to do this? Are Content Types the way to go?

The reasons I want to do it this way is:

1) I want my users to have one repositiory to look thorugh for all forms, regarldess of new or old.

2) I don't have two different libraries with two sets of views I need to keep in sync.

3) Our process has changed enough that many of the old fields are no long used so I will pull them from the web form.

Thanks for your suggestions!
Kelly