In Infopath 2010
I am using digital signature in section.
I am hiding that section but I cannot able hide digital signature.
View Complete Post
I have an Infopath browser based form that I have a digital sig on. When the user signs it (Valid Signature - Signed by) the font size is small and is acceptable for use in the form. Howvever, when I go to "Print View" it resizes to a larger
font. I do not want this as I am trying to fit the form to one page. I altered the font in the signing section in the Print View in Infopath to no avail. Looking at the Manifest file, I cannot locate the code where it determines the font
size. Anyone have any ideas?
I have a whole bunch of forms contains errors like whenever you try to open it up.
Infopath cannot load this form. Either the signature is corrupted, or the certificatie used to sign this form is expired or revoked.
The forms were orginally created with digital signature with it. But we were in the middle of transition from one company to another company. The digital signature was
no longer valid. Actually, the certificate should have been expired by now. I removed all the signatures for all of the forms. So they can continue using the forms to fill in the information. The problem right now, is trying to
open the old forms with digital signature on it. Not only the company has changed. We also moved sharepoint from the old server to the new server.
Any idea to resolve th
I’ve create a workflow project with infopath in it. And I get the error
“Error occurred in deployment step 'Activate Features': Unable to locate the workflow's association data. To restore
the association data to the workflow, restart the workflow settings wizard by selecting the workflow node in Solution Explorer and then clicking the ellipsis button (…) on one of the properties in the Properties window that has an ellipsis button.”
I'd really appreciate of any help.
I have an interesting issue while deploying a VSTO enabled form today. For
some odd reason while performing stsadm -o verifyformtemplate -filename
foobar.xsn, it returned a "FatalError : The form cannot be converted because
it was designed for a later version of InfoPath Forms Services.".
Has anyone else tried deploying a InfoPath 2010 form with managed code in a
MOSS environment?? I'd hate to go back to InfoPath 2007, I love the new
I found an issue when testing existing InfoPath 2007 forms via the Infopath 2010 Designer client. Integer fields in the form template are publishing to a SharePoint Forms Library and show in the default view. However, if that library is then
used as a Data Connection in another or same form template those integer fields are not displaying or available for selection.
This is not a problem using the InfoPath 2007 client. It is not an option to convert the field to text as it could affect existing forms in existing libraries. Also, existing integer fields are no longer appearing in previously defined SharePoint-based
secondary data connections. Only the ID field still appears. But, those existing fields still work in the form and are selectable for functions, etc.
Is there a solution to this?
Thanks much! Mike - www.ProgramNetInc.com
I need help or a push in the right direction. I am creating new forms for sharepoint2010 using infopath2010. Trying to make it so if someone hits an option button it activates an optional section or something simular. basicly if someone answers yes I have
more questions for them and dont want them to show UNLESS they say yes.
as always please and thank you
I've got an Infopath 2010 Form which i publish to a Forms Library in SharePoint 2010. In this form is a people picker field which i promote to the library but it gets promited as a text field and i cannot make it promote as a People or Groups data type.
I've set up my workflow to try and populate another column which i created (this one is a People or Groups column) with the promoted value but it doesnt do anything at all.
So now i cannot use the [Me] filter on either of the columns!!
How can i work around this?
We have several users who need permissions to edit a template and publish that template to the forms library.
The primary designer creates the template and uploads to a doc library. Admin staff from all divisions need to be able to flesh out the template and publish for all users.
I have built an InfoPath Filler form that I deployed to a SharePoint 2010 Form Library. While deploying, I checked that the form could be opened up using a web browser. I receive a warning that
the form template has been published to the server but if can only be opened in InfoPath Filler.
This is a problem, because it was decided that the form would be required to be opened using the browser. I made changes to the form so that it abided by the rules which allow it to be opened using a broswer (There were no design checker warnings or
This is the second form that had this problem. To fix it the first time, I simply created a new form that was not a filler form. Now that it has happened again, I wonder if there is a way to convert the filler form to a web browser form to save
Can this be done? Any other suggestions?