Allow us to develop custom modern forms with custom edit experience
We would like to be able to create an SPFx form and associate it with the List/Content type Disp, Edit, New form so that no matter how a user finds a list item (search, OOB list view, custom list view, etc) they see our custom form. Currently our only option is to create a completely disconnected experience in which we write a custom list view that points to custom form pages.
Alternatively support field customizers with edit model to enable custom field editing experience.
Jonathan Eckman
shared this idea
Thanks for your feedback! We’re reviewing your suggestion.
31 comments
-
Eric Zhao
commented
we really need this function
-
Uros
commented
PowerApps forms look ugly and the Office Fabric UI with React is both super snappy and elegant. Please think about the Developers and clients who want solutions that look professional.
For example, I want to create a custom form where users can select a folder in a library, then they can click a button in the modern experience little section above, then a form pops up where they enter metadata relating to the group of documents and a destination they would like it to go, after which the folders are routed to the new destination (doc library) and all the metadata is assigned. Completely self-service, elegant, simple and beautiful.
Sometimes I feel you are pushing the Citizen Developer angle too hard and leaving behind the very people you are trying to reach with SPFx (e.g. Developers).
-
Fredrik Thorild
commented
Look at this demo and listen to Vesas comments in the end - I agree with Vesa, do not use in production - if you do it is a potential can of worms, but we all know several ISV's and beyond are solving problems hacking the DOM. https://www.youtube.com/watch?v=2kYusJ1cGV4
-
Hans Sissing
commented
I have looked at using a powerapp, but that really is not an option, since we deploy a webpart and assets(fields, contenttype and list) in a site collection using an spfx solution. Multiple site collections get our app installed. The app-created list can be duplicated in the site collection, using the same contenttype. The list needs field customizers for create and edit. The only logical solution is to allow for customized edit experience on field level.
-
Alexandru Birsan
commented
is this becoming a thing anytime soon?
-
Russell Gove
commented
Quick note for anyone who is interested... If you set your list to use classic mode, then you can edit the page and hide the default form and add a spfx webpart. This has been working in our production environment for years (spfx 1.2 maybe?)
-
Mohd Tahir
commented
We are going to SharePoint 2019 because of SPFx option is there but we are confuse now because there is no custom form option yet.
One more very important point i'll highlighted here.
Market is now frustrated with Microsoft ever changing SharePoint development strategy with every new version, why you not make mature SharePoint development road map?
2007: SharePoint server side object model
2010: Sandbox can cure cancer and solve world hunger problem
2013: Sandbox solutions are obsolete, let's try SharePoint apps
2019: We have modern sites, let's start from scratch and now it is on cloud.we bit disappointed with development road-map.
You know still in market not much genuine resource available.
This is the drawback I think you seen coming years.
-
pirmas
commented
This is long overdue!! Please implement the change
-
Olof
commented
We need this
-
suraj patil
commented
Yes. We badly need this feature as SPFX provides powerful customization right in the front end. Many business requirement can be fulfilled with this approach only.
-
Manish Kaushal
commented
We need this feature badly for our Intranet as we are looking to standardize OOTB forms with our own custom design and SP Fx is the way to go so it should be a must have feature.
-
Anthony White
commented
This would be a logical next step in the SPFx evolution. PowerApps has issues for corporates with requirements over governance and ALM. The other third party forms products are expensive...
-
Christine
commented
Template saving needs to be an option for modern pages as well. Sharepoint is used not only for internal team support but also to manage the content flow for various clients. From an efficiency standpoint, it makes no sense to have to keep creating site layout over and over again. Considering the older version had it, Im not sure why it was taken away.
-
Rob Pearmain
commented
I have the scenario where a list has a look up field (room), and there are 1500 rooms, so I need the user to filter by building and then floor before choosing the room (the lookup field), so the ability to write a custom extension for this field would be fantastic
-
Terry
commented
100% agree! The clients I have require this capability before they will move from older SP versions to Online.
-
Gary Walker
commented
This would be really useful,
in the last few months we have had one client move away from O365 due to their complex workflow requirements, and another we are having to develop an spfx set as a single webpart part to deliver the complex business logic required by our client, loosing many of the out of the box features of SharePoint, PowerApps have no ALM when used as list forms, which makes it impossible to use when you must push through multiple environments for delivery.
Fredrik Thorild's suggestion would be perfect solution, we don't need a ui, just the ability to set these programmatically -
Anonymous
commented
Customized forms are the biggest source of value from SharePoint for my company. The business logic we've implemented is far too complex for PowerApps to handle, so this is our biggest hurdle for switching to the modern experience.
-
Anonymous
commented
Yes 👏🏻
This is badly needed, PowerApps should not be the only option.
Essentially forcing a customer to use another “product” to deliver this customisation is not the way to go.
-
Anonymous
commented
This would be a huge step in the right direction.
Going the PowerApps route is of course helpful in some scenarios, but as these can only be associated with Lists and not Document Libraries (another feature request exist for that as well), this does not solve all the problems.
-
Fredrik Thorild
commented
A simple way of enabling us is to open the opportunity to associate another url on the list default forms (this throws an error atm for modern xp). If this worked we could just point to a sharepoint page where we have our SPFx customization or even an AAD secured website elsewhere. I.e.
_list.DefaultNewFormUrl = "/SitePages/custom-new-form.aspx";
