Promoting Properties – Expose InfoPath Fields as Site Columns

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


Deploying InfoPath forms Using Features – the Right Way

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 ;) ] ]

Feature.xml

Element.xml

################### 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. 

THE LAUNCH !!!

It all started three+ years back a point of time when I was nurtured enough to find the information I wanted through Internet search, be it technical or general some way or the other I land up in a blog. Specifically that time SharePoint 2007 was in beta and there was very limited information over internet on the subject, As I saw most of the blog from the SharePoint Product team I was in a perception that blogs are meant to them, Later which I came to know about Blogspot which allows you to have your personal blog, I started one, but as there were so much to learn in SharePoint and have to spent all of my time in R & D to get the things working for my First ever Web CMS site based on SharePoint 2007, which was almost ready when the SharePoint RTM came out. I didn't find time to update my blog. Another thing I hate about blog is the Editor I didn't like the editor provided by the Blogspot as it is so small and was not able to type the content with ease. I didn't know about the tools (Word 2007 / Live writer ) that will help you to do that with ease. Later I got inspired with Wordpress for the rich set of tool it provide and the full screen functionality, which is when I started this.I was kind of used to update the blog at least twice a month.

As I started more blogging, I saw some pain points.Wordpress is pretty good at what they do and one limitation I was so concerned with the Wordpress/Blogspot is that I don't have more control on the template and the layout.I wanted to have more control on the website layout. I wanted to have more space for my content and it should be presentable to the user who is reading it. Soon I decided to have a blog for my own. I wanted it to be flexible enough I ran through couple of options, upgrade my Wordpress account, but it wont allow me to change the layout even If I upgrade, also Wordpress is running on PHP, I wanted my blog to running in something from Microsoft stack, ASP.NET. I was impressed by the theme used by Reza but then it was based on PHP Wordpress. I finally know what my blog should look like but I didn't know how to search for that template. Later I came across Tim site and it was running on ASP.NET. I mailed him and got the information that he uses Subtext Project as the blog engine. I then found that the theme used by Reza was inove from Wordpress. Last weekend I spent whole time to get the theme applied in the Subtext. Next item was to chose a good provider and buy a host name. Lot of options, I was looking at everydns for getting a host name for free and net4 to host my site, but everydns didn't work for some reason and net4 site is itself slow, It didn't look good. Finally I got all under ZnetIndia, customer support is so cool and got complete thing wired with in 1 Hour. I had to setup the subtext with IIS 7 as you need to configure the App Pool to run in  the Integrated Classic more else you will end up in httpModule issue.

And after all this here is what it looks like. Thanks for reading it through so far and I would like to have a comment if you have one on my blog. I will be happy to share this site theme, if you want  just leave me a comment. Also I have planned to concentrate only on SharePoint SharePoint SharePoint and bit of .NET & ASP.NET.