Skip to main content

Publish different InfoPath forms into a single library

Versions used in this article: InfoPath 2010 and SharePoint 2010

Recently, there was a need to use single library to hold multiple InfoPath forms. This was achieved by publishing InfoPath forms as Content Types. Here are simple steps to achieve this.

1.    You need a library which stores forms Content Types.
2.    Publish form as content type.
3.    Add Content type to forms library.
4.    Add different forms using content type.

Let me detail it out.
1.    Create a library or use any existing document library to hold the forms content types.
2.    Open InfoPath Designer
    a.    Design the form as per your need.
    b.    Save the form in your machine.
    c.    Go to File->Publish->Select SharePoint Server.
    d.    In the wizard, enter your site URL.
    e.    Next, select the option “Site Content Type”.
    f.    Next, select “Create a new content type”.
    g.    Next, Type name and description for the content type.
    h.    Next, select/type the document library URL which you have created in step 1.
           Here towards the end of path, type the name for the file (.xsn is automatically added).
           You can see how this form gets uploaded at step “j” below.
    i.    Next, select columns and define parameters (optional and as per your need).
    j.    You can verify the information. If everything looks fine, click Publish.
          Wait till you get success message. Click on Close to dismiss wizard.
3.    Go to the forms library
    a.    Go to Library settings -> Advanced settings.
           Ensure that “Allow management of content types” is set to Yes.
    b.    Under Library settings, under Content Types, click on “Add from existing site content types”.
    c.    Select the newly created content type.
4.    In the forms library,
    a.    Go to Documents tab, click on “New Documents” menu.
    b.    You can your newly published content type. Select the content type and fill up the form and Save.

Follow the above steps# 2-4 for different types of InfoPath Forms.
Labels:

Comments

  1. AnonymousApril 30, 2013 at 12:20 PM

    This comment has been removed by a blog administrator.

    ReplyDelete
  2. AnonymousApril 30, 2013 at 12:21 PM

    infopath
    I am always following your blog! Your blog posts helped me a lot and in different issues. More then this, I recomended the blog to all my colleagues. Thank you for the great job you do!

    ReplyDelete

Post a Comment

Popular posts from this blog

Document ID Service - New Feature in SharePoint

When I explored this new feature of SharePoint in Online (this feature is available in SharePoint 2013 also), I found it interesting because it solved one of the common problems people faced in SharePoint. I will first explain about this feature and I'll cover the problem and the solution in another post. This feature allows Site Collection Admin assign a unique ID to every document in the site collection out of the box. If you recall, there was no out of the box way to assign a unique number to the documents across libraries in a site collection. Yes ID column is unique but only within a library. Document ID column contains a number which is unique across libraries. To start with, let's have a look at a typical document library. This is a familiar view for SP guys. By default, you don't get Document ID column in a library. All Items View To get Document ID column, you need to activate a site collection feature "Document ID Service" as shown below. S...
Post a Comment
Read more

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this: data: { "__metadata": { "type": "SP.Data. ListName ListItem" }, "Title": "First Item", " PeopleField Id": "4" }; The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns. How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post! The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in peop...
12 comments
Read more

Restrict Future or Past Date in List

Many a times you will come across a requirement wherein you need to restrict user from entering future or past date in a List or Document Library Date column. Developers are inclined towards writing either event handler or javascript to achieve this. But, hold on! You can achieve this without writing a single line of code. I have a list which stores Employee details like Employee Number, Name and Date of Joining. Here I need to enure that Date of Joining will not accept future date. Navigate to List Settings -> Validation Settings. Here you can enter the formula to restrict future date as shown below. If you change the logical operator, it will restrict past date. Also, you can put message which will be displayed to user. Now, when you try to enter future date and try Save, you will see the validation message. So, next time you have similar requirement, you know where to try first before jumping into coding!
14 comments
Read more