SharePoint 2016 custom forms not rendering sharepoint:formfields when migrated to sharepoint 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1728522%22%20slang%3D%22en-US%22%3ESharePoint%202016%20custom%20forms%20not%20rendering%20sharepoint%3Aformfields%20when%20migrated%20to%20sharepoint%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728522%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20having%20an%20issues%20with%20Custom%20New%2FEdit%20and%20Display%20Forms%20in%20SharePoint%202019%20on%20Prem%20classic%20experience%20(not%20using%20PowerApps%20nor%20is%20it%20currently%20an%20option)%26nbsp%3B%20the%20form%20controls%20are%20not%20rendering%20on%20the%20page.%26nbsp%3B%20The%20title%20and%20Description%20Controls%20are%20rendering%20fine%20but%20the%20input%20controls%20are%20blank%20and%20in%20the%20DOM%20are%20appearing%20as%26nbsp%3B%3CSPAN%20id%3D%22%26quot%3BWPQ19103594b-6607-4669-9971-e170bd299ed9PhoneNumber%26quot%3B%22%20data-sp-options%3D%22'%7B%26quot%3Bmode%26quot%3B%3A3%2C%26quot%3Bsource%26quot%3B%3A%26quot%3BPhoneNumber%26quot%3B%7D'%22%20data-sp-control%3D%22%26quot%3BSPFieldText%26quot%3B%22%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Einstead%20of%20the%20correct%20markup.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20come%20across%20this%20in%202019%20and%20if%20so%20does%20anyone%20know%20what%20might%20be%20causing%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Visitor

I am having an issues with Custom New/Edit and Display Forms in SharePoint 2019 on Prem classic experience (not using PowerApps nor is it currently an option)  the form controls are not rendering on the page.  The title and Description Controls are rendering fine but the input controls are blank and in the DOM are appearing as <span id="WPQ19103594b-6607-4669-9971-e170bd299ed9PhoneNumber" data-sp-options='{"mode":3,"source":"PhoneNumber"}' data-sp-control="SPFieldText"></span>

 

instead of the correct markup.

 

Has anyone come across this in 2019 and if so does anyone know what might be causing it?

0 Replies