Can't change Content Type name in Site Designs

[sympmarc]

Category

• Enhancement
• Bug
• Question

Expected / Desired Behavior / Question

When we make a change to a Content Type name in a Site Design, we expect to see that renaming reflected in the site when we reapply the Site Design.

Observed Behavior

Content Type renaming is not applied with updates to the Site Design.

Steps to Reproduce

Create a simple Site Design such as this:

{
    "$schema": "https://developer.microsoft.com/json-schemas/sp/site-design-script-actions.schema.json",
    "actions": [
        {
            "verb": "createSiteColumnXml",
            "schemaXml": "<Field Type=\"DateTime\" DisplayName=\"Document Date\" Required=\"FALSE\" EnforceUniqueValues=\"FALSE\" Indexed=\"FALSE\" Format=\"DateOnly\" Group=\"_Milestone\" FriendlyDisplayFormat=\"Disabled\" ID=\"{c2452c8c-45f9-40a3-9b49-9b69d6a26b16}\" StaticName=\"DocumentDate\" Name=\"DocumentDate\" CustomFormatter=\"\" CalType=\"0\" Customization=\"\" AllowDeletion=\"TRUE\" />",
            "pushChanges": true
        },
        {
            "verb": "createContentType",
            "name": "Custodian - Other",
            "id": "0x0101002F0C592348AD1D4D8714CEF8AD8EC6D50305",
            "description": "",
            "parentId": "0x0101",
            "hidden": false,
            "subactions": []
        }
    ]
}

Add it to a Site Design and apply it to a site. Change the Content Type name (perhaps from Custodian - Other to Other Custodian) and reapply the site Design. The change will not be reflected in the site.

[msft-github-bot]

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

[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.