SharePoint / SharePoint/sp-dev-docs

SharePoint lists open default forms

Open
#10,870 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:spfx-extensions area:spfx-in-lists type:bug-suspected
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

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
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details
  • browser version
  • SPFx version
  • Node.js version
  • etc
Describe the bug / error

The list has a form SPFx extension. It is deployed via the content type property (such as NewFormClientSideComponentId). Starting Friday on some tenants the lists ignore the property and open the default form. Was there a recent rollout that is causing the bug?

Steps to reproduce

Only causes issues on some tenants

  1. Deploy a form customizer SPFx solution
  2. Set the component ID to the NewFormClientSideComponentId of the list content type
  3. Open New form. It opens the default list form instead of the form customizer form.
Expected behavior

Open the form customizer form from the solution. It has worked for many years with no issues.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SharePoint Online form customizer deployment described in the issue, especially the content type's NewFormClientSideComponentId and the affected tenant behavior. Reproduce the steps in Edge or Chrome and compare tenants where the custom form opens with those where the default form opens. Done means identifying the rollout or documenting a confirmed cause and workaround.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.