Showing results for 
Search instead for 
Did you mean: 
Advocate III
Advocate III

Cannot use "new experience" form editor when PCF component is on the form

I've created a PCF control that is working as expected in the model-driven app during runtime.  However, when I need to edit the form itself, I can only use the Classic Editor.  If I attempt to open the form editor in the "new experience" I receive an error message that in the form editor that prevents me from seeing any of the fields/sections/tabs on the form.


The error message appears as an error dialog in the form editor.  It states "Error.  Something went wrong.  Check technical details for more details."  However, I cannot click the technical details link.


Has anyone experienced this before?


If the PCF control is removed from the form, the "new experience" will work fine.


NOTE - I am not talking about configuring the PCF control itself, which I understand has to be performed in Classic.  To clarify, the issue here is that I cannot use the "New Experience" form editor at all when there is a PCF control on the form.



My PCF component is using WebAPI and Util features.  It is also using React.

Super User
Super User

Hi  @NewcombR , 


I think this is the same issues, as RAWilson's post:

Microsoft is working on it, as you can see in the answers.


If it's really the same issue, in order to avoid duplicates, should we close this thread?


Kind regards,



Helpful resources

Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.


Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Users online (7,945)