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 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 InfoPath-detail.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

SiteId

Unique identifier of the impacted site collection.

SiteURL

URL to the impacted site collection.

SiteOwner

Owner of the site collection.

SiteAdmins

List of people listed as site collection administrators.

SiteSizeInMB

Size of the size collection in megabytes [MB]

NumOfWebs

Number of webs that exist in the site collection.

ContentDBName

Name of the content database hosting the site collection.

ContentDBServerName

SQL Server hosting the content database.

ContentDBSizeInMB

Size of the content database hosting the site collection.

LastContentModifiedDate

Date/Time the site collection had content modified.

TotalItemCount

Total number of items found in the site collection.

Hits

Number of requests logged for the site collection. Relies on data from the usage logging service. If the usage logging service is disabled this row will show N/A.

DistinctUsers

Number of distinct users that have accessed the site collection. Relies on data from the usage logging service. If the usage logging service is disabled this row will show N/A.

DaysOfUsageData

Number of days the usage logging service retains data. This provides context for Hits and DistinctUsers. For example, if this is 14 days, the Hits and DistinctUsers data is for the last 14 days.

URL

Locations of the XSN.

URN

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

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.

UnsupportedDataConnectionTypes

Data connections that are not supported on the new platform.

UnsupportedDataConnectionCount

Number of unsupported data connections.

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.

PeoplePickerCount

Number of people picker fields found in the form.

SolutionFormatVersion

This field is no longer used and can be ignored.

ProductVersion

Version of InfoPath used to publish the form.

ScanID

Unique identifier assigned to a specific execution of the SharePoint Migration Assessment Tool.

Expand your skills
Explore training
Get new features first
Join Office Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×