Skip to main content

SharePoint 2013 - "No lists or libraries with InfoPath content types can be found"

I ran into a snag the other day after publishing an InfoPath form (as a Content Type) to one my SharePoint 2013 sites.  I was able to successfully publish the form to the Form Templates library.  Next step was adding the form to the page using the InfoPath Form Web Part.

Problem

When attempting to configure the Web Part I ran into this:
The message clearly states that "No lists or libraries with InfoPath content types can be found."

Solution

Please check the following depending on how you published the InfoPath form within your environment.

When publishing InfoPath form as a Content Type:
  1. See that the InfoPath form is being published to the same site as where the page with InfoPath Web Part is.
  2. Make sure that the Library (Form Templates) where the form is being published to has Content Types enabled.
  3. Enable Content Types on the Form Library where the form is submitted to (I'm assuming you are using a Forms Library other than the one in Step 2 for this).
  4. The form Content Type added to the Library where forms are submitted.

When publishing InfoPath form without a Content Type:
  1. See that the InfoPath form is being published to the same site as where the page with InfoPath Web Part is.
  2. Make sure that the Library you're publishing to is a Forms Library.


Comments

  1. World Trending TopicsNovember 3, 2017 at 4:56 AM

    Very Useful information Thank you!!
    TWB_ pioneered the offshore creation of technology content which was hitherto created by companies either internally or with ‘consultants’ hired by companies from vendors. TWB_

    changed that by creating domain depth that mirrored the customer’s own technology capability with deep SME teams for a variety of industries including Information Technology,

    Defence& Aerospace, Engineering, Life Sciences. TWB_ Creates, Automates, Repurposes and Publishes Content.


    ReplyDelete

Post a Comment

Popular posts from this blog

SharePoint 2013 - Simple Glossary using "HTML Form Web Part"

Introduction At some point you probably thought about incorporating glossary functionality as a part of a larger solution, or perhaps you were simply looking for providing a more intuitive way of filtering hundreds of items within a List or Library. Now there are countless web parts out there that you can either purchase or download from the SharePoint Store free of charge, and they all come with their own set of bells and whistles.  However, if you are looking at building one yourself, well look no further. To accomplish this we will need three major ingredients: SharePoint Page (either Wiki or Publishing will work) SharePoint List/Library with some content (Files/Items) HTML Form Web Part Let's Implement In this post I’m using a simple Wiki page, but you can also use a Publishing page as well.  We just need a canvas to display our glossary. I presume you already have a list or library that contains some content which is applicable to this concept....
12 comments
Read more

Remove Orphaned Web Parts - MissingWebPart

At some point you may have encountered an error like this while browsing through the SharePoint Health Analyzer or if you are attempting to test your content database (i.e., Test-SPContentDatabase) prior to mounting it. Message reads something like this: One caveat is that the log message never reveals the Location of the culprit web part.  Luckily we can utilize T-SQL to query the content database and reveal the location of the web part in question.   Query the Content Database To do this fire up the SQL Server Management Studio either locally from your machine or while logged on to the SQL Server back-end of your SharePoint farm, open up the new Query window and enter the following statement: USE < Content_Database_Name > SELECT AllDocs.SiteId,WebId, Webs.Title as 'Web Title', ListId, DirName,LeafName  FROM AllDocs    inner join AllWebParts on Alldocs.Id = AllWebParts.tp_PageUrlID  inner join Webs on Alldocs.WebId = webs.Id...
4 comments
Read more

SharePoint 2013 - Start a Site Workflow using a Custom Action

In recent travels I've encountered what seems to be either a product limitation or a bug. After digging around some it appeared that I wasn't the only one facing this challenge, and unfortunately there wasn't a concrete enough solution or workaround out there. Hence the blog post hoping to save some of you the unnecessary hair-pulling which I had to endure. My task was fairly simple; "Start a Site Workflow using a Custom Action button". The first part, creating a Custom Action, is trivial. This can be done in Visual Studio or SharePoint Designer. For the sake of simplicity I used SharePoint Designer. Create a Custom Action button Start up SharePoint Designer 2013 and connect to the desired site. From the left navigation select Lists and Libraries. I'm using a simple list called "List One". Boring name, but easy to follow. :) Click on the list name to manage list settings. From the ribbon select Custom Action button then click View Ribb...
Post a Comment
Read more