InfoPath Dev

About 18 months ago, my company did a partial upgrade to SP2013 and all of my forms failed. Not sure why becaue they upgraded the sites, not the worksites. I had to rebuild all the people-pickers with UDCX. Now my company is completing the upgrade by updgading the worksites as well which is where my forms reside; however, they provided a site collection upgrade in a Staging environment using the same URLs. When I test in the Staging environment, I get an error stating the Target application is not found (application id: SecureStore) - SecureStore is my Data Connection library for all of the UDCX files . Since the relationship of my forms and the UDCX library will be the same when they upgrade, is this just a matter of the forms not being able to locate the UDCX files now in the Staging environment and all will be well in the upgrade? We cannot afford to have the forms go down again for a month while I try to fix them one at a time. I need to sign off that the upgrade will be okay, but my testing in Staging is failing.

 I'm sorry, I'm super confused by your description. Why would people pickers need UDCX files? People pickers don't require a data connection to my knowledge....

We had a bunch of 2007/2010 people pickers that used the old Claims-based connection for GetUserProfileByName and we received instructions (I think from Qdabra) that all of these data connections needed to be converted using "Convert to Connection File: Convert this connection to use settings in a new data connection file stored in a Data Connection Library on a Microsoft SharePoint Server...i.e., udcx...called SecureStore.

The forms we haven't converted to Web-base yet, work fine (they open in Filler). The Web-based forms produce this error: Warning: There has been an error while processing the form. Click OK to resume filling out the form. You may want to check your form data for errors. ERROR DETAILS: Target application not found (application id: SecureStore)...bla bla bla.Correlation ID: bla bla bla.

The SecureStore is the snipet of Code I have to replace in the UDCX file in the Data Connection Library.

 The Data Connection Library is in the Staging environment and the URLs are all the same so it seems the physical relationship between the files is the same, as is the URL references, but still the errors for any forms where we had to convert the people-pickers or that use GetUserProfileByName to provide user identification.

My fear is that if this is not just a Staging configuration issue, when they convert our worsites from 2010 to 2013...I'm going to have another very long month trying to get back up and running.

 People pickers don't on their own use or execute data connections. However, if you were using GetUserProfileByName data connections, you will start seeing issues if you aren't setting the account query param correctly prior to executing the query - generally for claims you want to take the substring of the user name function after "|" to set the query field, then execute the data connection. However, if for some reason you are also using secure store in your UDCX, you need to be sure that app id exists on whatever server you have the form deployed to.

substring-after(userName(), "|")