Feedback by UserVoice

I suggest you ....

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.

921 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Jonathan Eckman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Terry commented  ·   ·  Flag as inappropriate

    100% agree! The clients I have require this capability before they will move from older SP versions to Online.

  • Gary Walker commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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";

  • Fredrik Thorild commented  ·   ·  Flag as inappropriate

    I have the same need and this is one of those "all I want for xmas..." Working with a huge client but their enterprise architects has not enabled PowerApps so we are really struggeling with presenting a good way to achieve a nice custom form experience in SharePoint

  • Guillaume commented  ·   ·  Flag as inappropriate

    Are you still thinking ? I Guess it is a pretty huge evolution, for the reflexion to take that long.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We would really need this in a lot of business cases.. powerapps is not enough and slow as soon as you start consuming custom API's with Flow etc on form load to for example hide / disable fields.. Please give us an update on the progress of this item.

  • Christopher Gronseth commented  ·   ·  Flag as inappropriate

    This right here is one of the reasons my company is stopping modern UI for our customers, powerapps forms is a JOKE, we need this to become a reality!

  • Sonyma commented  ·   ·  Flag as inappropriate

    Please simply make the new forms extensible same as it was with the classic forms. The #1 advantage of using SharePoint was its extensibility feature...remember?

  • Alex K. commented  ·   ·  Flag as inappropriate

    Will it be possible to modify values before saving? That would be really nice for a use case we have.

  • cbarnes commented  ·   ·  Flag as inappropriate

    The ability to configure these fields would be great as well. Maybe a properties panel like the spfx web parts.

  • Shai commented  ·   ·  Flag as inappropriate

    I don't get how this is a user voice suggestion and not the first thing on your plate. Got thousands of customers who can't use the new experience due to this lack of compatibility with customization they rely on, not to mention leaving consultants and vendors to take all the heat.

  • Alex Terentiev commented  ·   ·  Flag as inappropriate

    Please, consider next enhancements to Field Customizer (and Modern List UI):
    1. implement modern Quick Edit mode
    2. Add "edit" mode to field customizer
    3. Make field customizers (both view and edit modes) applicable on forms, panels, quick edit mode, etc.

Feedback and Knowledge Base