Quantcast
Channel: SharePoint Legacy Versions - Using SharePoint Designer, InfoPath and Other Customizations Forum
Viewing all articles
Browse latest Browse all 2319

Difference between "uploading" and "publishing" InfoPath template; permissions to publish?

$
0
0

Hello:

I am working with InfoPath 2010, and Sharepoint 2007. I have been beginning to learn how to use Sharepoint and InfoPath together using a "sandbox" Sharepoint site which has been created for me by the managers of our Sharepoint site.

I would like to practice publishing an InfoPath form to my Sharepoint site. However, the administrators of the site seem very cautious about this, and I believe I have not, (as I understand it), been granted enough permissions to publish an Infopath form.

I have two questions:

1:

I don't appear to have permissions to publish InfoPath forms, but I seem to be able to "upload" a copy of a form template which I've published to a network share. I have uploaded this template to a "Forms Library", and when I click on it, a download process happens, and the form opens. I can then fill in and save the form to a network location. How does this process compare/contrast to actually "publishing" this template? Is it an "ok" thing to do or is is wrongheaded?

2:

I had the impression that one of the benefits of Sharepoint would be that it was intended to give everyday users the power to create and manipulate objects and documents, such as InfoPath forms. Are the administrators being paranoid not to permit me to publish InfoPath forms? Is there a chance that there is a way to permit the publishing of forms that is safe and doesn't require a high level of permissions? Or is publishing an infopath form a security risk and, as such, should only be done by system admins? I just wish I could publish my own InfoPath forms so that I could teach myself more about this...

 

Thanks!

Fred


Viewing all articles
Browse latest Browse all 2319

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>