SharePoint 2013 Upgrade - InfoPath Dev Sign in | Join | Help in SharePoint Integration InfoPath (Entire Site) InfoPath Dev InfoPath Dev is dedicated to bringing you the information and tools you need to be successful in your Microsoft Office InfoPath development projects. Home Blogs Forums Photos Downloads InfoPath Dev » InfoPath » SharePoint Integration » SharePoint 2013 Upgrade SharePoint 2013 Upgrade Last post 06-10-2016 03:59 PM by Hilary Stoupa. 1 replies. Page 1 of 1 (2 items) Sort Posts: Oldest to newest Newest to oldest Previous Next 06-06-2016 08:16 PM JesseTam Joined on 01-20-2015 Posts 3 SharePoint 2013 Upgrade Reply Contact Believe we have been running Infopath 2010 and have certain libraries with > 500 submitted forms. This weekend our site upgraded to Sharepoint 2013 and now we are unable to edit our infopath forms. We are receiving an error message stating unable to submit, the file is currently checked out to (the same user trying to edit). Looking for any assistance possible since we have so many forms already submitted. 06-10-2016 03:59 PM In reply to Hilary Stoupa Joined on 06-20-2008 Posts 13,297 Re: SharePoint 2013 Upgrade Mark as Not AnswerMark as Answer... Reply Contact Hi - I think you work for a company we have done some work for, since I was involved with a conversation on a very similar issue earlier this week. :) In the end, they just needed to relink the forms in the library. Hilary Stoupa Page 1 of 1 (2 items) Copyright © 2003-2019 Qdabra Software. All rights reserved.View our Terms of Use.
Believe we have been running Infopath 2010 and have certain libraries with > 500 submitted forms. This weekend our site upgraded to Sharepoint 2013 and now we are unable to edit our infopath forms. We are receiving an error message stating unable to submit, the file is currently checked out to (the same user trying to edit). Looking for any assistance possible since we have so many forms already submitted.
Hi - I think you work for a company we have done some work for, since I was involved with a conversation on a very similar issue earlier this week. :) In the end, they just needed to relink the forms in the library.