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. /AdamQuestion on Site Scripts, Site Designs and Content Types
I work for a large University with a few dozen distinct departments, both academic and administrative. For the past month or so, I've been working on a Leave Request system/process/App and trying to build it in a manner that facilitates deployment at the department level (because many departments have their own unique requirements and will want to customize this). So, the basis of the system I created is a Content Type, defined in our Content Type Hub, called "<University> Leave Request". This CT is applied to a custom List (called "Leave Requests") in a SP site. There is also a PowerApp that uses that list as a data source and three different Flows that are connected to that App (Leave Submission, Leave Change, Leave Cancel). I know the PowerApp and related Flows can be packaged for (relatively) easy redeployment; the data sources would need to be updated each time, but since they're based on a Content Type (see, I was thinking ahead there), the column names, etc. will be exactly the same each time (barring customizations, but that's a given). Now, the problem I'm facing is how to streamline the creation of that Leave Requests list in a given SP site when a department wants to use this solution. List Templates still exist, so that's one option. We also have a license for Sharegate (for now, while we're in our "migration" phase), so we could use that, too. However, it seems MS wants folks to use Site Scripts and Site Designs for this sort of thing nowadays. In looking into that option, I saw this: Currently we do not support adding enterprise content types. I suspect that "enterprise content types" are those NOT "out of the box" (like my Leave Request CT), but I can't find anything to support or refute that suspicion. In researching this, I also learned that there are limits to the number of Site Scripts (100 per tenant) and Site Designs (50 per tenant, I think?), so I'm not sure I want to "burn" one of them for this purpose.
