SharePoint SPFx extension deployment options

Shailesh Jaiswal 81 Reputation points
2022-11-05T18:51:57.437+00:00

There are two XML files - elements.xml whose scope is site collection and ClientSideInstance.xml whose scope is Tenant wide.

If we set elementManifests property to elements.xml then can we deploy application extension, field customizer extension and command set extension to both site collection app catalog and Tenant app catalog?

If we set elementManifests property to ClientSideInstance.xml then can we deploy application extension, field customizer extension and command set extension to both site collection app catalog and Tenant app catalog?

SharePoint Server Development
SharePoint Server Development
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Development: The process of researching, productizing, and refining new or existing technologies.
1,596 questions
0 comments No comments
{count} votes

Accepted answer
  1. Rob Windsor 1,961 Reputation points
    2022-11-06T09:37:30.773+00:00

    Application customizer and list view command set extensions support tenant-wide deployment, which enables administrators to indicate they want the extension to automatically be available in all site collections in the tenant when deploying to the tenant app catalog or in the target site collection using the site collection app catalog. Administrators do this by selecting Enable this app and add it to all sites option in the Enable app dialog when using the modern app catalog experience or by selecting Make this solution available to all sites in the organization when using the classic app catalog experience.

    Please note that when deploying to a site collection app catalog, the prompt to Make this solution available to all sites in the organization is misleading. Despite the wording, when this option is selected the solution will only be made available in the target site collection.

    257594-image.png

    257596-image.png

    Doing this adds a list item in the Tenant wide extensions list, which is contained in the same site as the Apps for SharePoint list. The values for the fields of this list item are configured in the ClientSideInstance.xml file. Each time the extension is loaded, it will get it's configuration from the appropriate item in the Tenant wide extensions list.

    Please note that the Tenant wide extensions list may be hidden. If this is the case you can get to it by adding /Lists/TenantWideExtensions/AllItems.aspx to the site URL.

    257651-image.png

    257467-image.png

    If the administrator chooses not to use tenant-wide deployment, that is they select Only enable this app in the Enable app dialog, then the app containing the extension will need to be explicitly installed in the site collections where it will be used.

    257468-image.png

    In this case, the properties of the CustomAction element in the elements.xml file are used for the configuration of the extension.

    To summarize, the ClientSideInstance.xml file is used with tenant-wide deployment and the elements.xml file is used when apps are explicitly added to site collections.

    For more information on tenant-wide deployment, see Tenant-wide Deployment of SharePoint Framework Extensions.

    2 people found this answer helpful.

0 additional answers

Sort by: Most helpful