SPFx 1.15 - Getting error when use form customiser to view existing list item in Classic mode

[ethanli83]

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

I'm getting an error below when I'm try to view an existing list item with form customiser in Classic mode.

Steps to reproduce

1. Create a Form customiser extension and deploy to a SharePoint site.
2. Create a new list.
3. Create a new item on the list.
4. Update the DisplayFormClientSideComponentId of the Item content type to the component id of the Form customiser component.
5. Switch to Classic mode.
6. Click on the item.

Expected behavior

The form customiser shows up correctly

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[ejazhussain]

@ethanli83 @AJIXuMuK

How do we do the following step? is it possible via PowerShell?

1. Update the DisplayFormClientSideComponentId of the a content type to the component id of the Form customiser component.

[ethanli83]

@ethanli83 @AJIXuMuK

How do we do the following step? is it possible via PowerShell?

1. Update the DisplayFormClientSideComponentId of the a content type to the component id of the Form customiser component.

I did it by a C# programming using CSOM, but I think you can archive this by PowerShell.

All you need to do is to update the ContentType.

Here is how I did it

using (var clientContext = new ClientContext("YOUR SITE"))
{
    var sString = new NetworkCredential("", "PASSWORD").SecurePassword;
    clientContext.Credentials = new SharePointOnlineCredentials("USER NAME", sString);

    var list = clientContext.Web.Lists.GetByTitle("YOUR LIST");
    
    // Load content type collection
    clientContext.Load(list, l => l.Title, l => l.ContentTypes.Include(c => c.NewFormClientSideComponentId, c => c.EditFormClientSideComponentId, c => c.DisplayFormClientSideComponentId));
    await clientContext.ExecuteQueryAsync();

    var contentType = list.ContentTypes.First();

    var componentId = "COMPONENT ID OF YOUR FORM CUSTOMIZER";
    contentType.NewFormClientSideComponentId = componentId;
    contentType.EditFormClientSideComponentId = componentId;
    contentType.DisplayFormClientSideComponentId = componentId;

    contentType.Update(false);

    await clientContext.ExecuteQueryAsync();

    Console.ReadKey();
}

[ejazhussain]

Thanks, @ethanli83 I have ended up writing similar code to update components Ids.

[AJIXuMuK]

@ethanli83 - the fix has been merged and will be rolled out WW in the next couple of weeks.

[ethanli83]

@ethanli83 - the fix has been merged and will be rolled out WW in the next couple of weeks.

Thank you very much~

[AJIXuMuK]

Should be rolled out WW by now

[ghost]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues