InfoPath development for Sharepoint

M

mreyeros

I have been given the task of setting up infopath to work with a custom
application that we are building that uses the sharepoint object model for
document management. What I need to be able to do is to:
1. Have the ability to filter form questions
2. Automate the recording of form questions
a. Ability to categorize form questions
3. Create template InfoPath form with embedded logic
a. Create webservice to feed infopath form


If anyone has any experience doing any of the above your help and insight
would be appreciated.
 
G

G. Tarazi

I am working on a software that uses InfoPath and share point +(SQL Server /
C# / XSL), some of our forms do submit their data to a web service, and then
the web service (c# code) does the rest, and some of them submit to Share
Point, and the event handlers (c# code) are doing the rest.



There are tons of possible scenarios, you can have the forms saving
everything in a share point library, and an event handler that you will
write in c# or vb.net will modify the form xml as needed, or will export a
copy of it to a database, or will create a new xml form file, etc.



You may also save a form to a web service, and have the web service storing
it to share point, or directly to a database, if stored in a database, you
will need to connect the share point to the database, or the web service,
and use an xsl to display the data properly.



You can also do most of the functionality in the form itself, using code,
but you must be careful, at on level the form may need to be signed and
fully trusted in order to be used, and that means hard to debug, harder to
develop, and not easy to install.



There are also other scenarios, depends on your project.



Good luck
 
M

Michael Reyeros

All the forms will be saved to a master forms library in my sharepoint. All
subsites will be able to access the master forms library and copy the form
from there into the subsites' document library. From here the form can be
filled out and saved to the document library. This is basically what we
want to accomplish.
 
P

ploneuser

Hi,

How can I know until which level it's possible to embed code in the
form itself?
I'm currently trying to submit a form to a sharepoint library. I need
to do some work before submitting because I'm also trying to embed a
workflow inside the form, that's why, when submitted I need to catch
the submit event and change the state...
But I'm facing a security execption, and I don't know what to do now...

Do you think it would be easier to submit the form to a web service and
do all the work in it?

Thanks,
 
G

G. Tarazi

Hi



In my case I am doing all the workflow, save, and load (to the database) in
the web service itself, although I have more than 500 C# event handlers in
the form, I am trying to keep all the functionality in the web services and
the related DLL files (to the web services).



Testing and debugging the code outside InfoPath is easier, the full .NET xml
capabilities are more powerful, you may use them inside InfoPath, but the
problem there is signing the form to be secure and trusted.



You can use the InfoPath event handlers to capture all events (including the
submit event) and perform any operations you want, but remember, if you are
using C# with InfoPath, each new event handler is = couple of mili seconds
delay during the first form loading.



If you have 300 event handlers, totally empty, and you try to load the form,
it may take the form up to 10 additional seconds to load (+ the original
loading time). (this problem is not available in the Java Script version of
InfoPath.




My suggestion is, have a web service that does everything, and keep the form
as light as possible, and to avoid the security exceptions, make sure you
are not using code like the System.XML namespace (use the InfoPath one
instead, etc) otherwise you will get security exceptions.



Or just trust the form and mark is as secure, but them debugging will not be
as easy as it used to be.



Good luck
 
Top