- Edit your Form Library page.
- Add a Content Editor web part to the page and move it below the form library.
- Open the properties for the Content Editor web part and add the path to the StopLight.txt file. Make sure you upload this file to the Site Assets library in the same site where your form lives.
- Set the Content Editor Appearance property to hidden and click OK to save the changes.
- Add a new calculated field column to the Form Library and call it Overall Status (you can call it anything you like).
- In the formula section add the following: StopLight Formula
- Save the new column and return to the Form library.
- Make any additional changes to the form library, for example set the Style to Newsletter to give it a neat professional look.
Download the StopLight.txt file here.
Any questions, let us know in the comments section below.
- Create a document library to store the InfoPath form content type.
- Publish the form as a content type to the site, save it in the new library created in step 1, then promote any new columns as site columns.
- Create a new form library and add the new content type as the default.
- Save a form from the old library by ‘downloading a copy’, then upload it to the new form library.
- Relink this form in the new library.
It should open and function as normal.
When you log into your SharePoint site, open a Form Library and click New to create a new InfoPath form item, you may see the error message “Activation could not be completed because the InfoPath Forms Services support feature is not present.”
This is a hidden feature and one that does not appear in the Central Administration user inferface.
Some forums out there suggest running the following stsadm commands:
- STSADM.EXE -o deactivatefeature -filename IPFSSiteFeatures\feature.xml -force -url %SITE_COLLECTION_URL%
- STSADM.EXE -o deactivatefeature -filename IPFSWebFeatures\feature.xml -force -url %SITE_COLLECTION_URL%
- STSADM.EXE -o activatefeature -filename IPFSSiteFeatures\feature.xml -url %Sitecollection_URL% -force
- STSADM.EXE -o activatefeature -filename IPFSWebFeatures\feature.xml -url %sitecollection_URL% -force
In general, you don’t need to run the commands above as the InfoPath Forms Services support feature is a hidden feature and is present by default unless someone turns them off manually.
For me, the solution was to turn on a different feature found at the Site Collection level called “Open Documents in Client Applications by Default” which can be found under Site Actions > Site Settings > Modify All Settings > Site Collection Features. Turning this feature ON opened the InfoPath forms in the InfoPath Filler program which is standard across the organisation.
So, if the above STSADM commands don’t do it for you, try turning on the “Open Documents in Client Applications by Default” feature.
Questions, comments welcome.
Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.
Problem: The form link in an email notification is meant to open in the InfoPath client application but instead it opens in a Browser.
Solution 1: Go to Form Library > Form Library Settings > Advanced Settings and change the option for “Opening documents in the Browser” to “Open in Client Application”
Solution 2: Log into the Farm, open Central Admin > General Application Settings > InfoPath Forms Services and uncheck the option to Render Forms in the Browser.
Solution 3: Open Site Actions > Site Settings > Modify All Settings. Under Site Collection Administration, click Site Collection Features and Activate the “Open Documents in Client Applications by Default” feature.
Join the Forum discussion on this post
Problem: InfoPath Items not showing up in Form Library.
1. Go to Form Library Settings > Advanced Settings and “Allow Management of Content Types”;
2. Click the “Form” content type and then Advanced Settings. In the next screen, click Edit Template to open the Form in Edit mode in InfoPath;
3. Right click the Submit button and click Properties;
4. Click Submit Options > Manage > Modify and check the Document Library path to ensure that it is pointing to the Library only and nothing more.
For example: http://servername/sites/testingworkflows/Derek%20Travel%20Form%20Library/
Join the Forum discussion on this post