Issue with deployment of List View Command Set Extention

[john88benson]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

When I bundle and deploy a List View Command Set Extension that checked out in test that it appears on a site it has been deployed on.

Observed Behavior

I built a custom solution for making a JSON Post to a MS Flow using the List View Command Set Extension. While it worked during gulp serve testing when I deployed to my tenant it would not appear.

I then back tracked and built out the basic extension based on the MSFT tutorial: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api

While it also worked fine during gulp-serve testing it did not appear when packaged and deployed to a site.

Steps to Reproduce

I have uploaded the project to Git Hub: https://github.com/john88benson/listViewCmdExtension

It is the "OOB" version of the ListViewCmdset stub created using the yo @microsoft/sharepoint (I updated my generator before hand: version 1.4.1). After confirming it functioned during gulp serve I ran a gulp clean, gulp bundle --ship, gulp package-solution --ship then loaded the package into my App Catalog. I added the App in the Site Contents for a site then checked for it in a Document Library but no dice.

Thanks for your contribution! Sharing is caring.

[john88benson]

You can close this item, it is not a bug. It's not obvious from the gulp serve testing but the RegistrationId in elements.xml specifies what type of list it appears on when deployed. Once I updated the Reg Id to 101 it started appearing in the Doc Library as expected.

It may be worth making this a little more explicit in the CmdSet Tutorial since the early steps show the extension working on a Doc Library but it will display only on generic Lists unless the Reg Id is updated.

Thanks,
-JB

[msft-github-bot]

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