View Updates in Site Designs Do Not Reflect Site Design Order

[sympmarc]

Category

• Enhancement
• Bug
• Question

Version

NA

Expected / Desired Behavior / Question

When we make a change to a view in a Site Design, we expect to see the columns in the view displayed in the order we provide

Observed Behavior

New columns are added to the right of the existing view, not the location specified in the Site Design.

Steps to Reproduce

Create a simple Site Design updating a view, such as this:

        {
          "verb": "addSPView",
          "name": "All Documents",
          "viewFields": [
            "ContentType",
            "DocIcon",
            "LinkFilename",
            "Modified",
            "Editor",
            "DocumentDate"
          ],
          "query": "<OrderBy><FieldRef Name=\"FileLeafRef\" /></OrderBy>",
          "rowLimit": 30,
          "isPaged": true,
          "makeDefault": true,
          "formatterJSON": ""
        }

Add it to a Site Design and apply it to a site. In this example, ContentType and DocumentDate will be added to the right of the existing columns in the All Documents view.

[msft-github-bot]

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

[sympmarc]

One might think the solution would be to set up a custom view, delete it, and then reinstate it each time the Site Design runs. However, this seems to throw an error:

I've tested with a Site Script which only deletes the existing view, and that verb is what is throwing the error. (Default View does exist, but this should work even if it doesn't.)

{
   "$schema": "https://developer.microsoft.com/json-schemas/sp/site-design-script-actions.schema.json",
   "actions": [
      {
         "verb": "createSPList",
         "listName": "foos",
         "templateType": 101,
         "subactions": [
            {
               "verb": "removeSPView",
               "name": "Default View"
             }
         ]
      }
   ]
}

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