SharePoint Views

Category: Infopath

Code Signing Certificate for Admin Approved InfoPath form template

Security level for admin approved code behind InfoPath form templates should be Fully trusted. Code Signing Certificate should be used to sign fully trusted InfoPath form templates before uploading to Central Admin. Go to File and Select ‘Form Options‘ under Advanced options Select ‘Security and Trust‘ in the left pane Code Signing Certificate: You can…

The form cannot be opened because either signature is corrupt or the certificate used to sign the form expired or revoked

You get the following message when you try to open an already submitted InfoPath form  – ‘The form cannot be opened because either signature is corrupt or the certificate used to sign the form expired or revoked’ when the certificate used to sign the form has expired or revoked. Even if you try to open the…

Clearing Infopath Cache

When you publish new version of InfoPath or update certificate for the form, some users may still see the old version or have issues with new certificate. Clearing InfoPath Cache in users machine resolves this issue. When user access an InfoPath form, it is usually cached in users machine. Whenever there is a new version of…

Migrate admin approved infopath forms in SharePoint

In my recent project, I have to migrate admin approved InfoPath forms in SharePoint 2007 to SharePoint 2010 . Admin approved forms are deployed as features at farm level. They are under 12 hive folder named with GUIDs. After some googling, I found handy STSADM and Powershell commands. Using these commands we can easily package and…

Best Practices for designing a Browser based Infopath form

There is no rule book explaining Best Practices for designing a Browser based InfoPath forms. Most of the times performance of the form depends on other factors such as volume of data, number of fields, design, overall farm performance, number of external connections, data rendering in the form(post backs) etc. In this blog I am going…

Infopath error using GetUserProfileByName method after converting to Claims or migrating to SP2013

When migrating your SharePoint 2010 InfoPath forms to SharePoint 2013 or while changing your classic web application to claims based web application, all the InfoPath forms which accesses user profile services(GetUserProfileByName method) fails with authentication errors. In claims based web application user name is prefixed with “0#.w|” .User name in classic mode is “domain\username”  but…