We are evaluating retiring the SharePoint Framework (SPFx) Field Customizers feature from SharePoint Lists and Document Libraries
We are evaluating retiring the SharePoint Framework (SPFx) Field Customizers feature from SharePoint Lists and Document Libraries. In many cases, we recommend alternatives like using Column Formatters and disabling SPFx Field customizers. This would help with better performance with modern experience that is continuously updated.
When this will happen
We are currently assessing the timelines and will update this post as plans progress. You can be assured that it will be communicated well in advance, with ample time to manage transition effectively.
How this affects your organization
There is no impact to your organization as of now. In future depending on updated timelines, SharePoint Lists or Document Libraries with SPFx Field Customizers may be affected:
-
Field Customizers will no longer render custom code.
-
Column data will display using the default rendering based on column type.
Other SPFx extensions, such as Command Set Customizers and Application Customizers, will continue to function as expected. We recommend transitioning to Column Formatting for visual customizations where possible. For scenarios requiring third-party code execution, continue using Command Set Customizers or Application Customizers.
What you can do to prepare
Review your current use of Field Customizers and begin planning your transition.
Use column formatting to customize Lists and Document Libraries
For visual updates to field rendering and display in SharePoint, it is recommended to use custom formatting, for example as detailed here.
For support for running third party code, Command Set Customizers and Application Customizers will continue to be supported and can be used to fill that need.
Find Field Customizers in your environment
As Tenant Admin or another user with sufficient permission, PnP PowerShell can be used to detect the presence of field customizers on a site like so:
get-pnpField | where-object { $_.ClientSideComponentId -ne [Guid]::empty }
Summary
We recognize that these changes may require additional work for some of our customers. We are encouraged by our customer successes, and our ongoing investment in List and Library modernization in Microsoft 365.
