Published March 1, 2021

Retirement of support for external XSLT files in DataFormWebPart and its subclasses

Reference ID: MC242207

MC242207 – To enhance data integrity and improve the overall reliability of the service, we are retiring support for external XSLT file references for the DataFormWebParts and its sub-classes (e.g. XsltListFormWebPart, XsltListViewWebPart).

This retirement affects only classic SharePoint pages.

Key points

  • Timing: mid-March
  • Roll-out: tenant level
  • Action: review and assess before March 15, 2021

How this affects your organization

Support for external XSLT files references in the DataFormsWebPart and its subclasses will no longer be available after March 14, 2021.

  • After March 14, 2021, the DataFormsWebPart will be unable to perform functions that rely on external XSLT code.
  • If you are currently using a DataFormWebPart that references external XSLT code, you will need to modify the reference to an internal XSLT file located in the site’s asset library instead. 

Potential scenarios for using the DataFormWebParts on classic SharePoint pages:

  • DataFormWebParts have been created via SharePoint Designer and include XSLT code
  • DataFormWebParts have been created and customized in the browser or via PowerShell to include XSLT code

What you need to do to prepare

Conduct an audit of DataFormWebParts for all classic SharePoint pages that may exist in your tenant. If you discover external XSLT references, remove them.

To retain the same functionality as before, use one of two methods:

  1. Copy the external XSLT files to the asset library of the same site on which the DataFormWebParts are hosted. Then reference the XSLT files from there instead.
  2. Consider using a modern solution such as JSLink for classic SharePoint pages, and SPFx or custom formatters for SharePoint modern pages and lists.

To enhance data integrity and improve the overall reliability of the service, we are retiring support for external XSLT file references for the DataFormWebParts and its sub-classes (e.g. XsltListFormWebPart, XsltListViewWebPart).

This retirement affects only classic SharePoint pages.

Key points

  • Timing: mid-March
  • Roll-out: tenant level
  • Action: review and assess before March 15, 2021

How this affects your organization

Support for external XSLT files references in the DataFormsWebPart and its subclasses will no longer be available after March 14, 2021.

  • After March 14, 2021, the DataFormsWebPart will be unable to perform functions that rely on external XSLT code.
  • If you are currently using a DataFormWebPart that references external XSLT code, you will need to modify the reference to an internal XSLT file located in the site’s asset library instead. 

Potential scenarios for using the DataFormWebParts on classic SharePoint pages:

  • DataFormWebParts have been created via SharePoint Designer and include XSLT code
  • DataFormWebParts have been created and customized in the browser or via PowerShell to include XSLT code

What you need to do to prepare

Conduct an audit of DataFormWebParts for all classic SharePoint pages that may exist in your tenant. If you discover external XSLT references, remove them.

To retain the same functionality as before, use one of two methods:

  1. Copy the external XSLT files to the asset library of the same site on which the DataFormWebParts are hosted. Then reference the XSLT files from there instead.
  2. Consider using a modern solution such as JSLink for classic SharePoint pages, and SPFx or custom formatters for SharePoint modern pages and lists.

Petri Newsletters

Whether it’s Security or Cloud Computing, we have the know-how for you. Sign up for our newsletters here.

Latest Posts on Petri.com

Latest Podcast

00:00

/

00:00