Command Set Extension triggering Command Set from different extension!

[Tanddant]

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

• Edge Version 135.0.3179.85
• SPFx 1.10.0 and 1.10.0

Describe the bug / error

I have two command set extensions deployed to the same list, both use the COMMAND_1 key, which I should probably have changed, but this has never been an issue before!

One opens a link, and the other a dialog, but that doesn't matter for the issue I'm facing.

When both command sets are visible in the command bar, pressing either will trigger the first one, however once they "rollover" into the overflow menu, they work as expected.

This is a solution that has been live for several years, however this only started about 3 weeks ago, we've been hoping it would resolve itself, but it hasn't.

I expect a new site to open when I press "Gå til tilbud" and the dialog to show when I press "Se serie" however (logging confirms) when I press "Se serie" and they're both visible the "Gå til tilbud" is triggered.

Steps to reproduce

1. Create two separate Command Set extensions, in separate solutions, leave the "COMMAND_1" key, and have them simply write a Console.log - something like "Hello World 🎉" and "Hello World 🥲"
2. Deploy them to the same list
3. Press the button while they're both visible in the ribbon.

Expected behavior

Each command set extension is it's own solution, I would never expect "cross contamination" between different SPFx Solutions.

I would expect to see the same behaviour no matter if they're in the overflow menu or the command bar

Video showing the issue

Video.mp4

[Ashlesha-MSFT]

Hello @Tanddant,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@Tanddant,
I’m seeing the expected behavior on my end.
However, one thing I did notice is that the same button appears for two different solutions, which seems a bit unusual.
Please let me know if there’s anything I might be missing or if there’s anything additional I need to check or do.

20250423-0508-07.0347395.mp4

[Tanddant]

@Ashlesha-MSFT, Yes, you're missing the whole point of my issue 😅 - once my command sets are in the overflow menu, they work as expected, the issue is when they're in the ribbon - once I then zoom so they go to the overflow menu, it works as expected.

Also important distinction, I'm in a document library, not a list, shouldn't make a difference, but with the way lists have been updated over the past year I wouldn't be surprised if it did affect it.

As for you seeing the button twice, did you tenant wide deploy them, AND install them on the list perhaps? 😊

[Ashlesha-MSFT]

@Tanddant,
Thank you for detailed explanation.
We were able to reproduce the issue. We have logged this as a bug, and our engineering team will look into it.
Thank you for your patience!
https://github.com/user-attachments/assets/7da993db-9c44-4dba-a781-7d1be1e6d936

[Tanddant]

@Ashlesha-MSFT - I know it's been summer and all, but this is a MASSIVE issue - we're having multiple clients affected, do you have any update?

This could lead to accidental deletions, sharing or alike - In the past I've built a "Permanently Delete" button, if that's triggered by accident from this bug, that's catastrophic?

[Ashlesha-MSFT]

@Tanddant,
Thanks for highlighting the critical impact of the issue. I’ve tagged the engineering team for updates and have requested their input on this. I’ll share any updates with you as soon as I hear back from them.