Site Script - Adding column to Site Pages is not inherited by Repost Page content type
Hi, Adding a column to the Site Pages library using the UI has the option "Add to all content types" which seems to be missing in Site Script. So, adding a site column via Site Script as below results that columns is only inherited by the Site Page content type and not the Repost Page. "actions": [ { "verb": "createSPList", "listName": "Site Pages", "templateType": 119, "subactions": [ { "verb": "addSiteColumn", "internalName": "PageCategory", "addToDefaultView": true } ... } Results in: This could be solved by modifying the base site content type: "actions": [ { "verb": "createContentType", "name": "Site Page", "description": "Create a new site page", "hidden": false, "parentName": "Document", "subactions": [ { "verb": "addSiteColumn", "internalName": "PageCategory" } ] }, { "verb": "createContentType", "name": "Repost Page", "description": "Used to create a News link post. If deleted, the News link option will be disabled for users.", "hidden": false, "parentName": "Site Page", "subactions": [ { "verb": "addSiteColumn", "internalName": "PageCategory" } ] }, { "verb": "createSPList", "listName": "Site Pages", "templateType": 119, "subactions": [ { "verb": "addContentType", "name": "Site Page" }, { "verb": "addContentType", "name": "Repost Page" } ... } So, to my questions: Is the approach with modifying the base site content type "OK" nowdays or is it violating any practices/rules? Reflections on this? If 1 is not OK then is it solvable using Site Design/Site Script or will it require alternative approach such as PnP? NOTE: Want to use Site Design/Site Script and would like to avoid creating own content type in this case. /Adam
Site Script Action Limit
Microsoft's documentation states: We'd previously capped the limit of site script actions to 30. This remains the limit for scripts applied synchronously using the https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/Invoke-SPOSiteDesign?view=sharepoint-ps command, but based on customer feedback and support for additional actions we have bumped this limit to 300 actions (or 100,000 characters) when the scripts are applied asynchronously (either through the UI or using the https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/Add-SPOSiteDesignTask?view=sharepoint-ps command). I created a script that has more than 30 actions, and indeed the Invoke-SPOSiteDesign command does not work; however, the Add-SPOSiteDesignTask does work. I assume that ..."through the UI" in the statement above refers to creating a site using the Create Site button in SharePoint. When I use the Create Site button with my design that contains the +30 action script. It does not work. I just get the message that it is Initializing, but nothing ever happens. If I cancel out of the operation and then use the PowerShell Add-SPOSiteDesignTask command, the design is applied as expected. What does Microsoft mean by "...through the UI"?
Azure Automation Runbooks using Powershell: Push notifications error?
I'm trying to run some PnP PowerShell commands in an Azure Runbook (e.g. Get-PnPContentType, Apply-PnPProvisioningTemplate, etc. ) over a SharePoint site, but it keeps returning the error below: The Push Notifications feature is not activated on the site The correct modules have been imported and it only errors on some commands. Running the commands in a PowerShell window with the same credentials doesn't produce any errors, and activating the 'Push Notifications' feature manually and retriggering the Runbook won't produce any error output, but will say that the Runbook failed to run 3 times.
