Today I was debugging an error in InfoPath Form, in particular InfoPath 2010 installed in an typical SharePoint Farm. Error was more generic and could deviating you from actual solution.
One or more ActiveX Controls could not be displayed because either:
1) Your current security settings prohibit running ActiveX controls on this page, or
2) You have blocked a publisher of one of the controls.
As a result, the page might not display correctly.
With this when you start you will obvious end up in links that will suggest some registry changes. And few links suggest you add web URL as trusted Site etc. After all these you will see the issue still.
After few tries you may change the query to see “Ink Control not working” which will lead you to results of articles taking about Ink Control not supported in browser enabled InfoPath forms.
At this point I figured, that It was something related to missing ActiveX control, Usually when you have Custom ActiveX control you need to deploy it to the system that will fill InfoPath forms, refer this link for details.But Ink Control is out of the box control and it should be part of system that has InfoPath Installed.
That is when I figured out that Ink Control is not for regular PC but it is intended to be used by Tablet PC users. So in fact error is right InfoPath filler could not locate the Ink Control Active X dll. How do we fix it, easy Install the Ink Control, which is part of Microsoft Windows XP Tablet PC Edition Software Development Kit 1.7. Once you Install InfoPath with Ink Control will just work fine.
Couple of take away here.
- You cannot expect end user system to have this SDK installed nor it is a corrective measure.
- Reason I said it is not a corrective measure is because of the fact, Ink Control was to help user draw something , not to capture user signature (what most people think and use this for)
- Refer this to see an example of how it is used also Microsoft suggest that we use Digital signature not Ink Control for capturing Signature (because of security).
- If you have a pressing need then you can package the ActiveX control and deploy as part of the solution.
Let me know your thoughts.
Well First Let me explain what does it mean by Promotion and Demotion
- Promotion – It means that you capture the value present in the document (*.xml or wordML or you can write your own document parser) and expose it to the SharePoint document library as a Column. What you get out of it is that you have a synchronization of the Data between the document and Column of the doc library. (When you update the document it gets automatically reflected in the document library and vise versa.)
- Demotion – It means the opposite. You capture the column of the Document Library and display it in the Document.
Well whenever you publish a InfoPath form to the SharePoint server using File->Publish, at the end of the Wizard you will be provided
with a Option that will allow you to the add the field of the InfoPath to the document. How can do that when I automation the publishing of the InfoPath using features or When I publish the form using Central Administration Website?. There is an option in InfoPath, where you can specify the fields to be promoted to the Document Library at the design time. Use Tools->Form Option -> Property Promotion
After going through this article, I got to know the power of Universal Data Connection UDC files in the InfoPath forms and how it helps during multiple deployment and migration scenarios. But what I missed to note is How do I get a Data Connection File from the Central Administration Site – > Manage Data Connection. This article describes how to do that. Also below I have highlighted the points that you need to get a file from Data Connection File from the Central Administration. (Managing the Data Connection Files centrally) with few quick screen clips that will help you.
Let’s assume that you have created an InfoPath form as per this article. To recap you have added the data connection from the Data Connection Library of your SharePoint site, while doing so you will find an option called Connection Options. Click on the Connection Options and Select the option centrally managed connection Library, by this what you mean is that you are asking the Form template to get the connection file from the Centrally Managed Connection Files from Central admin.
From now on your InfoPath form template will get the Connection Setting from the UDC File of the Central Admin. In case if you want to make any changes to the connection setting all you have to do is to change the Connection File present in the Central Administration Server.
A week back couple of my friends was asking is there a proper way to deploy the InfoPath forms to the server, Way other than File -> Publish – > SharePoint server with or without forms server. I did a quick search and was not lucky, came to a lackadaisical conclusion that there is no other way. But whenever I deploy workflows with InfoPath form I see a new solution that adds itself to the Solution Store. By this I know for sure there is some other way to deploy InfoPath forms. First thing want I wanted was to get the Solution out of SharePoint and see what’s there inside, Again for this there is a tool through which you can do it [I lost the url from where I got it] or hardly 10 lines of code is all what you need.
To my surprise there is indeed a way to do it, well let’s see how. What I got out of that solution is a feature, what’s in it [Image speaks louder than words, image with comments even louder 😉 ] ]
################### You are Right its again another File Provisioning in to SharePoint Lib #####################
############# Be sure to put the location as FormServerTemplates############
Here is the Stripped Out Version of the XML.
Steps in Short:
- Develop your IP form.
- Publish it to the network location as how you do to upload to the Central Administration Upload Form Templates.
- Create one Feature.xml, Element.xml as defined in the article [Sorry how workflow does ;)].
- Put in the IP form and create a feature out of it.
- Its all.
It was hard for me to understand how the InfoPath form services licensing work and how it is related to SharePoint server 2007 (MOSS 2007). I stumbled to find the link “Manage InfoPath Form Templates” in my local Development environment which is a Standard SharePoint CAL installation. Today I Googled it and managed to get few information regarding it.
- We know that InfoPath can be viewed in the browser without InfoPath Client.
- How? Well InfoPath Form Services help you to render the InfoPath form in the Browsers without InfoPath client installed in your machine.
You can get the InfoPath Form Services in two ways (Assuming that you have a Standard SharePoint 2007 Installation or WSS 3.0 Installation).
- Buy a License for Microsoft Office Forms Server 2007 and install it in your SharePoint / (WSS 3.0) Server Farm. [This is the only option in case if you have the WSS 3.0 Installation]
- Upgrade your SharePoint Server farm to the Enterprise License. [Form Services Features are supported in Enterprise Version].
If you still want to get confused more J . Please refer to the below links that give you the information on the various SharePoint licensing favors.