More efficient method of removing Data Connection orphans? - InfoPath Dev Sign in | Join | Help in Data Connections 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 » Data Connections » More efficient method of removing Data Connection orphans? More efficient method of removing Data Connection orphans? Last post 03-18-2013 08:30 AM by khoyle. 2 replies. Page 1 of 1 (3 items) Sort Posts: Oldest to newest Newest to oldest Previous Next 03-12-2013 08:46 AM khoyle Joined on 03-12-2013 Posts 2 More efficient method of removing Data Connection orphans? Reply Contact Our team is currently converting InfoPath2010 forms that have been previously developed for SharePoint workflow (using GetUserProfileByName & other data connections) to using K2 workflow. One of the first conversion steps is deleting the previously used Data Connections, which leaves a bunch of orphaned fields. Aside from going through the Manifest and/or form fields, is there a more time-efficient way to find out what was orphaned? Thanks in advance Kelvin 03-18-2013 08:00 AM In reply to Jimmy Joined on 07-03-2008 Posts 2,595 Re: More efficient method of removing Data Connection orphans? Mark as Not AnswerMark as Answer... Reply Contact Could you clarify what you mean by "orphaned fields?" Are you referring to controls that were previously bound to the removed data sources, or something else? Jimmy Rishe / Software Developer / Microsoft MVPQdabra Software 03-18-2013 08:30 AM In reply to khoyle Joined on 03-12-2013 Posts 2 Re: More efficient method of removing Data Connection orphans? Mark as Not AnswerMark as Answer... Reply Contact Yes, these are controls that are bound to the removed data sources. Thanks! Page 1 of 1 (3 items) Copyright © 2003-2019 Qdabra Software. All rights reserved.View our Terms of Use.
Our team is currently converting InfoPath2010 forms that have been previously developed for SharePoint workflow (using GetUserProfileByName & other data connections) to using K2 workflow. One of the first conversion steps is deleting the previously used Data Connections, which leaves a bunch of orphaned fields. Aside from going through the Manifest and/or form fields, is there a more time-efficient way to find out what was orphaned?
Thanks in advance
Kelvin
Yes, these are controls that are bound to the removed data sources.
Thanks!