Site Script for associateListViewCommandSet always failed

[robbenwangcn]

Hi,

I have a SPO ListViewCommandSet extension which uploaded to the tenant app catalog and can successfully added in sharepoint sitecollections manully.

I wanna to install the app within the Sharepoint Site Design. But the task alway run failed. Can anyone help on this ?

Site Scripts:
{
"$schema":"schema.json",
"actions":[
{
"verb":"createSPList",
"listName":"Documents",
"templateType":101,
"subactions":[
{
"verb":"addSPFieldXml",
"addToDefaultView": true,
"schemaXml":"<Field ID="{a8793ace-8e95-4dca-8970-5bb2710f567a}" Type="Choice" DisplayName="Tag" Required="False" Format="Dropdown" StaticName="Tag" Name="Tag">NANAControl DocumentNon-Control Document"
},
{
"verb": "associateListViewCommandSet",
"title": "GPMSCommandSet",
"location": "ContextMenu",
"clientSideComponentId": "64ccd979-8814-4e31-9ddf-18b1b7198503"
}]
}
],
"bindata":{},
"version":5
}

Sharepoint Online Management shell result:

OrdinalIndex : 0
SiteScriptID : 61a69424-bafa-4955-9c03-ebb70eb1ae12
SiteScriptTitle : GPMS SiteScript 6
SiteScriptIndex : 0
ActionIndex : 0
ActionTitle : Create or update library "Documents"
ActionKey : 00000000-0000-0000-0000-000000000000
OutcomeCode : NoOp
OutcomeText : List with name Documents already exists.

OrdinalIndex : 1
SiteScriptID : 61a69424-bafa-4955-9c03-ebb70eb1ae12
SiteScriptTitle : GPMS SiteScript 6
SiteScriptIndex : 0
ActionIndex : 0
ActionTitle : Add list column "Tag"
ActionKey : 00000000-0000-0000-0000-000000000000
OutcomeCode : Success
OutcomeText :

OrdinalIndex : 2
SiteScriptID : 61a69424-bafa-4955-9c03-ebb70eb1ae12
SiteScriptTitle : GPMS SiteScript 6
SiteScriptIndex : 0
ActionIndex : 0
ActionTitle : Associate command set "GPMSCommandSet"
ActionKey : 00000000-0000-0000-0000-000000000000
OutcomeCode : Failure
OutcomeText : Something went wrong and we could not complete this action.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 68267476-ee8d-7b95-446b-711ddb683da2
• Version Independent ID: aa099b9d-48db-5513-11c7-32c49a27e5be
• Content: Site design JSON schema
• Content Source: docs/declarative-customization/site-design-json-schema.md
• Product: sharepoint
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

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

[bcameron1231]

Hi, can you confirm the extension is a tenant wide extension and is available on the site before your site script runs? If not, you'll want to make sure you add an installSolution or associateExtension to registered a deployed SPFX solution from the Tenant App Catalog.

[robbenwangcn]

Hi Cameron,

My extension is a tenant wide extension. After I create a new site , I can see my extension in the "From your Organization", and can manually add it without any issue. picture below is the result after manual add.

[robbenwangcn]

@bcameron1231
Any updates? thanks in advance.

[bcameron1231]

Hi, can you share the values for package-solution.json for your solution?

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.