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 command: spo tenant commandset remove #4867

Closed
Tracked by #4219
martinlingstuyl opened this issue May 12, 2023 · 2 comments
Closed
Tracked by #4219

New command: spo tenant commandset remove #4867

martinlingstuyl opened this issue May 12, 2023 · 2 comments
Assignees
Milestone

Comments

@martinlingstuyl
Copy link
Contributor

martinlingstuyl commented May 12, 2023

Usage

spo tenant commandset remove

Description

Remove a ListView Command Set that is installed tenant wide.

Options

Option Description
-t, --title [title] The title of the ListView Command Set. Specify either title, id or clientSideComponentId.
-i, --id [id] The id of the ListView Command Set. Specify either title, id or clientSideComponentId.
-c, --clientSideComponentId [clientSideComponentId] The Client Side Component Id (GUID) of the ListView Command Set. Specify either title, id or clientSideComponentId.

Examples

Removes an ListView Command Set by title.

m365 spo tenant commandset remove --title "Some command set"

Removes a ListView Command Set by id.

m365 spo tenant commandset remove --id 3

Removes a ListView Command Set by clientSideComponentId.

m365 spo tenant commandset remove --clientSideComponentId 7096cded-b83d-4eab-96f0-df477ed7c0bc

Additional Info

Removes the list item from the tenant wide extensions list.

  • If multiple items are found, a disambiguation prompt should be given back to the user.
  • Should only look for items of the type ListView Command Set. (Compare with spo tenant applicationcustomizer get command implementation)
  • The id property is the list item id of the item in the TenantWideExtensionsList
@nicodecleyre
Copy link
Contributor

Can I work on this one?

@milanholemans
Copy link
Contributor

Please do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants