Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New UI Document library web part command bar is empty when custom listvew command set is used #10077

Open
2 of 9 tasks
s-KaiNet opened this issue Jan 13, 2025 · 6 comments
Open
2 of 9 tasks
Labels
type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@s-KaiNet
Copy link
Contributor

s-KaiNet commented Jan 13, 2025

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

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

Latest SPFx version.
Build version received from "X-MS-Meta-Sourcebuild" header: odsp-web-prod_2025-01-03.009 for document list web part
JS error in dev console:

Uncaught Error: Resource #347 "GetOverrideSpfxCustomActions" is being consumed, but is not available in the current scope.
  1) Check to ensure that the dependency on this resource (and each step up the chain) is properly declared.
  2) If availability is expected, check to see if the target resource has a dependency that is only available in a child scope.
  Required by Resource #693 ""
  Required by Resource #348 ""

obraz

Describe the bug / error

When you have a SPFx list view command set extension, the command bar for document library web part isn't loaded at all:

obraz

Steps to reproduce

  1. Create a new sample list view command set extension with at least one custom button. Don't change any code, just use the default one generated by yeoman.
  2. Register command set to a document libraries (ListTemplateId="101")
  3. Deploy command set globally.
  4. Add document library web part to a page.
  5. Command bar for the web part is not loaded.

Expected behavior

The command bar along with custom commands is loaded normally:

obraz

@s-KaiNet s-KaiNet added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label Jan 13, 2025
@s-KaiNet s-KaiNet changed the title New UI Document library web part command is empty when command set is used New UI Document library web part command bar is empty when custom listvew command set is used Jan 13, 2025
@JonEOffice
Copy link

JonEOffice commented Jan 13, 2025

I would like to join this suspected bug in that I have a customer with two tenants who also faces this problem. The document library webpart command bar is empty and all the buttons are gone on the page when a custom command is present in the document library

@Haiqi-Wu
Copy link

Haiqi-Wu commented Jan 14, 2025

List Web Part is the same situation. All command bar buttons missing.

@dalejo09
Copy link

dalejo09 commented Jan 14, 2025

I have same situation using a custom SPFx ListViewCommandSet Extension.

On list, all native and custom buttons are working as I spected but on page when I use a "Listview webpart", buttons are not appearing in command bar in Microsoft Lists UI and commad bar is empty .

When I disabled my custom ListViewCommandSet on TenantWideExtensions, the command bar works well on list and on page but the problem is when I have a custom ListViewCommandSet applied. Yesterday this custom SPfx was working well

My custom SPfx are on SPfx 1.15.x

Thanks to help with this bug

@reedpamsft
Copy link
Contributor

We have a fix for this and are looking at the best path to roll it out.

@Haiqi-Wu
Copy link

Looks like it's fixed.

@s-KaiNet
Copy link
Contributor Author

We also don't have this issue on our tenants anymore. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

5 participants