K2 blackpearl Product Documentation: Installation and Configuration Guide
InfoPath and SmartObjects issue with Re-publish

Troubleshooting - InfoPath and SmartObjects issue with Re-publish

An issue occurred while using InfoPath and SmartObjects and attempting to Re-publish the InfoPath form.

Scenario

The following scenario existed:

An InfoPath process integrated with a K2 process with a number of SmartObjects as secondary data sources. While attempting to deploy from development to a testing environment, the following steps were performed:

  1. Changed the K2 Object Browser to the target environment.
  2. Performed a clean up of the project.
  3. Performed a deployment to the target environment (just to make sure the project is all setup for the proper environment).
  4. ‘Designed’ the InfoPath Form from the InfoPath Integration Wizard in the process.
    1. Changed something on the form.
    2. Reviewed the Data Sources (the data sources were all pointing at the proper staging target .asmx file)
    3. Saved and closed the InfoPath Form
  5. The K2 InfoPath Wizard then auto-refreshed.
  6. Stepped through the wizard and completed the wizard.
  7. Performed a clean up of the project. 
  8. Re-publish the project (just the particular process).

Problem

So at this point, an XSN should exist that fully points to the target (staging) environment. The problem is, however, that this is not the case. The actual data source xml files (when you extract the innards of the published XSN) all still have the <_soServer> node pointing at the development environment.

Since the forms needed to be code-signed, the Re-publishing was done manually. Unfortunately the wrong form was used (the xsn from the K2 project was used instead of the xsn from SharePoint) 

Solution

To fix the <_soServer> data source XML inside the InfoPath form so that it points to the new environment's correct SmartObject Server, it is important to note the following.

The xsn in the K2 project folder doesn't represent what was published to SharePoint. The xsn published into SharePoint has all the correct values. So if you need to do a manual Re-publish as a result of needing full-trust code-signing and/or form services, retrieve the xsn out of SharePoint and modify that one, not the one from within the K2 solution.

 

 


K2 blackpearl Product Documentation: Installation and Configuration Guide 4.6.10