SharePoint / SharePoint/sp-dev-docs

Debugging field customizer not working in "new" SPO lists

Open
#9,842 5 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Apr 28, 2025.

area:spfx area:spfx-extensions Needs: Triage :mag: sharepoint-developer-support type:bug-confirmed type:bug-suspected
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details
  • browser version 127.0.2651.86
  • SPFx version 1.19.0
  • Node.js version 18.20.1
  • Using WSL 2 on Windows 11
Describe the bug / error

On my dev tenant I got a new SharePoint list design.
image

I can not debug my SPFx Field Customizer with this new design. The component is loading (I checked with CTRL+F12 in SPO and I can see the manifest and js files loading in the terminal) but it is never executed.

On my live environment with the old list design everything is working as expected.

Steps to reproduce
  1. Create an SPFx solution with a Field Customizer
  2. Change the serve.json to the correct field name (in my case its "Percent")
  3. Run it on a Tenant with this new list design
Expected behavior

The list should render the field like this:
image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.