求助：使用PnP/CSOM自定义SharePoint新建OOTB文档库的配置问题

Hey there! I’ve run into this exact scenario before, so let’s break down how to get your custom content types and site columns applied automatically whenever a new document library is created—whether via the classic addanapp.aspx page or modern site pages.

1. Create a Reusable Custom Document Library Template (PnP Provisioning) #

The simplest approach is to turn your already-configured library into a reusable template that users can select when creating new libraries. Here’s how to do it with PnP PowerShell:

• First, export the configuration of your working library into a PnP template:

  Get-PnPSiteTemplate -Out CustomDocLibTemplate.xml -ListsToExtract "YourConfiguredLibraryName" -IncludeAllContentTypes -IncludeSiteColumns
  

• Next, you can either:
  • Let users import this template directly when creating a new library (via PnP PowerShell or the PnP Provisioning Engine), or
  • Upload the template to your site’s List Template Gallery (/_catalogs/lt/Forms/AllItems.aspx) so it appears in the "Create" menu alongside default options.

This way, users just pick your custom template instead of the default Document Library, and all your content types/columns are pre-applied.

2. Use Site Scripts & Site Designs (Modern Experience) #

For modern site pages, you can define a site script that applies your custom configurations automatically when a new document library is created. Here’s how:

• First, craft a JSON script that defines adding your content types and columns to a document library:

  {
    "actions": [
      {
        "verb": "addContentType",
        "contentTypeId": "0x010100YOURCONTENTTYPEIDHERE",
        "targetList": "Shared Documents"
      },
      {
        "verb": "addField",
        "fieldType": "Text",
        "displayName": "Project Code",
        "internalName": "ProjectCode",
        "addToDefaultView": true,
        "targetList": "Shared Documents"
      }
    ],
    "version": 1
  }
  

• Then use PnP PowerShell to register the script and link it to a site design for document libraries:

  # Add the site script
  $script = Add-PnPSiteScript -Title "Custom Doc Lib Config" -Content (Get-Content -Path "YourScript.json" -Raw)
  
  # Create a site design tied to document library templates
  Add-PnPSiteDesign -Title "Custom Document Library" -WebTemplate "101" -SiteScripts $script.Id
  

Now when users create a new library via modern pages, they can select your "Custom Document Library" design, and all your configurations are applied automatically.

3. Auto-Apply Configs with SPFx Extension (All Experiences) #

If you want to enforce that every new document library (no matter how it’s created) gets your content types/columns, use an SPFx List Added event receiver:

• Build an SPFx extension that listens for the OnListAdded event across your site.
• In the event handler, use PnP JS to apply your configurations to the newly created library:

  import { BaseListViewCommandSet, ListAddedEventArgs } from '@microsoft/sp-listview-extensibility';
  import { sp } from "@pnp/sp";
  
  export default class CustomDocLibConfigExtension extends BaseListViewCommandSet {
    public onInit(): Promise<void> {
      return super.onInit().then(() => {
        sp.setup({
          spfxContext: this.context
        });
      });
    }
  
    public onListAdded(args: ListAddedEventArgs): void {
      // Only target document libraries (template type 101)
      if (args.listTemplateType === 101) {
        const targetList = sp.web.lists.getById(args.listId);
        
        // Add your custom content type
        targetList.contentTypes.addById("0x010100YOURCONTENTTYPEIDHERE")
          .then(() => {
            // Add custom site column if it doesn't exist
            return targetList.fields.addText("ProjectCode", "Project Code", true);
          })
          .catch(err => console.error("Error applying configs:", err));
      }
    }
  }
  

• Deploy this extension to your site and ensure it’s activated for all web scopes. Now every new document library will get your setup automatically.

4. Override the Classic Default Template (for addanapp.aspx) #

If you need to fix the classic addanapp.aspx experience specifically:

• Go to your site’s List Template Gallery (/_catalogs/lt/Forms/AllItems.aspx)
• Download the default "Document Library" template (ID 101) as an .stp file
• Extract the .stp (it’s a zip file), open Manifest.xml, and add your content type and column definitions directly into the template’s XML
• Re-zip the file, rename it back to .stp, and upload it to the gallery to overwrite the default template

Now any library created via the classic add app page will use your modified template with custom configurations.

Choose the approach that fits your environment—for most modern SharePoint setups, combining a custom template with an SPFx extension gives the most reliable coverage.

内容的提问来源于stack exchange，提问作者Steve Johnson