Sp-dev-docs: SPFx ListViewCommandSet extensions are not loaded in List webpart

Created on 11 May 2020  路  24Comments  路  Source: SharePoint/sp-dev-docs

Category

  • [x] Bug

Describe the bug

We have several different List View Command Set extensions deployed to different tenants. We use them in lists and also in the list webparts in modern pages. On Thursday (May 7th) we noticed that extensions are no longer being loaded in the list webparts. They work fine in the lists.

There are no errors in the DevTools console from extensions.
All pages have a weird error from sp-pages-assembly "_Telemetry manager failed to initialize. Error: Logging buffer overflow hit before any logging handler was registered_". But I'm not sure if this is relevant in any way.

Extension files for List View Command Set extensions are not loaded from cdn.
Field Customizer extension still works fine in the list webpart, all files for it are loaded.

I tried completely deleting and re-installing extension in one of the site collections - no help.

Steps to reproduce

  1. Go to site collection where ListViewCommandSet extension is installed
  2. Check that extension is loading in the list
  3. Open any page and add a List webpart
  4. Extension doesn't show up, no extension files are loaded from cdn

Expected behavior

We expect List View Command Set extension to show up in the command bar of the List webpart

Environment details (development & target environment)

  • OS: Windows 10
  • Target Environment: SharePoint Online
  • Framework: Node.js v8
  • Browser(s): Chrome v81, Edge
  • Tooling: SPFx v1.10.0
spfx-extensions bug-suspected

All 24 comments

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

Dupe of #5704?

I don't think so. I can reproduce their issue as well. But it their case, I can see all the extension files loaded from the cdn. Looks like it just doesn't get triggered.

In our case, none of the List View Command set files from CDN are loaded for the List webpart. No mater if we open page directly, or from navigation

I have the same problem.
We don't know if it is a bug on Office365/SP Online, or if something has changed in listview command set extensions development/configuration to allow this kind of components to be displayed on list webparts.

Please, we have several customers using this feature.

Thank you

We also have the same problem, the buttons went missing (or we just noticed) same time this was posted. We did some digging and it seems this issue already occurred before? here

We were able to make it work until this issue so I'm not sure but maybe its just a manifest change or something for this to be fixed?

Please advise. Thanks.

Can confirm this. Using this feature a lot in our solutions. If we can have a fix soon it would be great.

Thanks.

I'm not sure if this is related or not, but our command sets although loading fine on the library at first will bug out on a partial page refresh (switch between libraries or filter by a column). Could the OP test this? Guess that would make it a dupe of #5704

Switching between the libraries also causes the extension to disappear for us. However, filtering or sorting by a column seem to work fine, extension keeps appearing and working.

Anyone with a workaround on this bug? I tried to register the commandset with registrationid 119 but the script is still not loading.

We haven't found any good workaround. We are considering remaking our extensions to the webparts or field customizer extensions since we need the functionalities to work and we can't wait long for a fix.
We registered this in M365 support too, but no news yet. If we get any information from the ticket, I will update this topic as well.

@mbijei I have a customer reported exact same issue which has been investigating by the team. Do you mind share the M365 support ticket # so I can link it to mine?

I am not being able to see the buttons when i add the document library webpart in a page. However the command set buttons are coming up in the corresponding document library

same issue

@aaronmi Sorry for long time to respond. Our ticket number is #:19924412. Do you mind sharing yours, so we can reference it too?

So far no good news from our ticket. M365 support said there were some updates done, but extension still doesn't work for us.

@aaronmi Sorry for long time to respond. Our ticket number is #:19924412. Do you mind sharing yours, so we can reference it too?

So far no good news from our ticket. M365 support said there were some updates done, but extension still doesn't work for us.

@mbijei we raised a ticket as well and the number of our ticket is #20284100

This morning all ListViewCommandSet extensions in the List webparts just started to work for us. I hope it's same for everyone else, thank you for sharing your experiences.

I still have the issue with the extensions disappearing when switching between lists in navigation (on partial load), but that's other ticket. ( #5704 )

Thanks... seeing other reports of the extensions working as well so I'll go ahead and close this.

Hello again! Actually, after working for a half of the day, extensions are gone from List webpart again. We see this in all tenants, for all of our List View Command Set extensions.

Hello again! Actually, after working for a half of the day, extensions are gone from List webpart again. We see this in all tenants, for all of our List View Command Set extensions.

Yes, issue is back again and I reopened the ticket at Microsoft side as well.

@mbijei and @jsidler, sorry for a long time to respond. My ticket# 20125412.
The MS product team had a fix and started rollout to Prod. Unfortunately, it was rolled back due to a critical regression issue in that build. A new build including the fix has started rollout to Prod since last Friday.

The new build containing the fix to the issue has been rolled out to Prod 100%. I verified that my LVWP with spfx extension is working now.

We can verify, that our extensions are working with the list webpart as well.

@mbijei and @jsidler, sorry for a long time to respond. My ticket# 20125412.
The MS product team had a fix and started rollout to Prod. Unfortunately, it was rolled back due to a critical regression issue in that build. A new build including the fix has started rollout to Prod since last Friday.

Thanks for your information. Today it looks like it works again. Hope it stays like this.

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

Was this page helpful?
0 / 5 - 0 ratings