Open diabhoil opened 1 month ago
Any news on this?
If I deploy the solution and set ClientSideComponentId of the field to the ID of the field customizer component I am able to debug. But that is not really a solution because it forces me to install a solution to the tenant which is not ready.
I have seen the issue #9873 but the workaround mentioned there - using the display name of the field in the url - is not working in my case.
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
Additional environment details
Describe the bug / error
On my dev tenant I got a new SharePoint list design.![image](https://github.com/user-attachments/assets/6487d2a6-4c11-402a-b1c6-f8a35831b679)
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
Expected behavior
The list should render the field like this:![image](https://github.com/user-attachments/assets/38a63631-94f3-4189-8433-e482994560e7)