We are in the process of upgrading to SharePoint 2013 and one of the sites just done is a forms repository. These are InfoPath forms created in InfoPath 2010. There are data connections that pull data from an external source (a SQL database) that no longer work.<o:p></o:p>
Our URLs start with https://cwe.xx.xxx (This is the old one) and https://cg.xx.xxx (This is the new one). The site and the Content Type Hub site created to house the paths (for lack of a better term) to the SQL database both are now in the new domain.<o:p></o:p>
When opening the form in the new environment the form errors that there are data connections trying access across domains and the fields that use the data connections are empty.<o:p></o:p>
HERE IS THE ERROR:<o:p></o:p>
A query to retrieve form data cannot be completed because this action would violate cross-domain restrictions.
If this form template is published to a SharePoint document library, cross-domain access for user form templates must
be enabled under InfoPath Forms Services in SharePoint Central Administration, and the data connection settings must be stored in a UDC file in a data connection library in the same site collection.<o:p></o:p>
---------------------------------------------------------------------------------------------------<o:p></o:p>
I have tried to modify the existing data connections through Info Path and cannot do so. I tried creating new data connections using the Search for connections on a Microsoft SharePoint Server option and I am able to point to the correct location. I go through the whole process of adding this data connection with no problems but the form will not publish using it. On the last screen of the wizard the Summary shows the SharePoint site as if it is still on the old domain. The message I get when I try to publish the form with that data connection is "The form template cannot use data settings from more than one site collection. Remove data connections that reference Data Connection Libraries on site collections other than the one you intend to publish to."<o:p></o:p>
The problem is I don't am afraid to remove the old data connections. If I remove the one I just created it publishes again fine. I tested this by just adding some text and then verifying it was there after publishing the form in the new domain.<o:p></o:p>
How does this work? How can I either modify my old data connections to point to and use the data connection library in the new domain or how can I add new ones that will work? The person that set this up initially is out of the country for 2 weeks and it has fallen on me now. She had our server admins run a PowerShell script before she left but it did not help.<o:p></o:p>
Any help or information that helps me resolve this would be greatly appreciated.<o:p></o:p>
Thanks you, <o:p></o:p>
Doug<o:p></o:p>
Other recent topics
