Retiring certain WebPartPagesWebService methods affecting web part migration

New SharePoint Feature

From Microsoft Corporation

MC221387, Plan For Change, Published date: Sep 2, 2020

Major update: Announcement

Applies To: All

We’ve identified an issue with five methods belonging to the WebPartPageWebService Application Programming Interface (API) that could cause impact to data integrity. These methods are AddWebPartAddWebPartToZoneSaveWebPartSaveWebPart2, and GetWebPartPageConnectionInfo. As a result, we are planning to retire these methods.

Note: If your organization is not utilizing these methods you can safely disregard this message.

Key points:

  • Major: Retirement
  • Timing: early October 2020 to mid-October 2020
  • Action: review and assess organizational impact

How this will affect your organization:

The affected methods in the SharePoint SoapServer were called primarily to migrate web parts from classic SharePoint sites to SharePoint Online. Once these methods are retired, they will no longer return any data. You can find alternative methods in the SharePoint Client-Side Object Model (CSOM) to achieve this functionality.What you need to do to prepare:

For admins and developers: If your software is currently calling any of the five aforementioned SoapServer endpoints, you’ll need to modify the software to instead call methods in the LimitedWebPartManager class of the SharePoint CSOM (version 16.1.20324.12000, or newer). This class includes a new HasWebPartConnections property that allows you to determine whether a web part page connection exists.

Learn more

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.