Migration Assessment Scan: InfoPath

Learn how to mitigate issues with InfoPath during migration.

Overview

InfoPath enables developers to build custom forms for accepting user input in a variety of locations throughout SharePoint. As part of the migration to the target environment, there are certain aspects of InfoPath forms that are not supported in the target environment.

Data Migration

InfoPath forms (XSN files) will be migrated, but some forms may not function without remediation.

Important: Any site that is configured as “No Access” (locked), in SharePoint will be skipped. To see a list of locked site collections see the Locked Sites scan output.

Preparing for Migration

XSN files that leverage the following scenarios will need to be remediated. If remediation does not occur, these forms will fail post migration. The common scenarios are as follows:

  • XSN or UDCX makes SOAP calls that are not supported in the target environment. These forms will need to be updated to call supported endpoints.

  • XSN leverages managed code that will require validation or remediation. Managed code is not supported on the target platform.

  • InfoPath forms that leverage people picker fields. These fields need to be updated with the new identity post migration.

Post Migration

Ensure the updated InfoPath forms function correctly during the migration user acceptance testing phase.

Scan Result Reports

The following table describes the columns in the InfoPathForms.csv report.

This scan report contains InfoPath forms that will require remediation prior to migration, or at a minimum, validation on the new platform.

Column

Description

URN

Unique identifier for the XSN file. Each XSN file will have a distinct URN.

InstanceCount

Number of URLs that the XSN was located in the SharePoint environment.

URL's

Locations of the XSN.

UnsupportedSoapCalls

SOAP calls that are not explicitly listed as supported by the target environment.

UnsupportedSoapCallsCount

Number of unsupported SOAP calls found in the XSN file.

ManagedCode

True - The XSN file has managed code associated with it. False - The XSN file does not have managed code associated with it.

ManagedCodeState

ValidationRequired - Managed code may work in the target environment. It will require validation during the migration testing phase to be sure.

RemediationRequired - The form has managed code that will require remediation.

Mode

The mode that the form was published in. For example, a mode of "Client" results in an InfoPath form that will only open in the InfoPath client. Whereas a mode of "Client Server" will open in both the browser and the InfoPath client. Forms with mode set to Client will not show up in this report.

ProductVersion

Version of InfoPath used to publish the form.

InfoPathForms_PeoplePicker_<Date>_<Time>.csv    This scan report contains InfoPath forms that leverage People Picker fields. These fields will contain the windows identity information that was set when the form was submitted.

Column

Description

URN

Unique identifier for the XSN file. Each XSN file will have a distinct URN.

InstanceCount

Number of URLs that the XSN was located in the SharePoint environment.

URLs

Locations that the XSN was located at.

SiteURLs

URL of the site collection hosting the form.

PeoplePickersCount

Number of people picker fields in the form.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×