Question 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.
Add a link to planner via addNavLink with a SharePoint site script?
Manually, it's easy to add a link to planner in the UI: edit the nav, add a link, and choose "planner" in the dropdown in the "add a link" dialog. Simple. The same option doesn't seem to be available via the addNavLink option with Site Scripts, as the https://docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/site-design-json-schema#add-a-navigation-link only mentions static URLs. Is there another way to determine the URL for the default Plan for a newly created site, as to be able to add it to the left nav as part of the site creation process?
Where to create an Office 365 group?
Right now there are LOTS of places you can create a new 365 Group from. Just to name a few I know of: Azure AD - Directly create a group SharePoint Team Site - Creates a group along with the site Microsoft Teams - Creates a group along with the team (can also make team from existing group) There are quite a few more ways that groups can get instanced, but the real issue here is the lack of symmetry. When a group is created, it gets a SharePoint Team Site regardless of where you make it, but if you make the group as a part of the process of making a new team site you can also select a site design to apply to that site. I have read that site designs can be applied to existing modern sites, but have yet to find out how to do that. If you create a group in Teams, a team is added and linked to the group, but if you create a group anywhere else no team is added! I am trying to build a system where a new Office 365 Group for a new project is created, a specific SharePoint site design/template is provisioned, and a Team is provisioned. Some other configurations are done using the site design script -> launch a flow feature. Can anyone help me understand where the "proper" place to first create a group is? Especially so that there are no lingering loose connections between services? This all seems like a bit of a mess right now.Any success with the new Site Design functionality?
The new Site Design PowerShell commands starting to work for me this morning so I created my first script and site design. The new design appears in the choices when I create a new team site but none of the actions in my script are followed. Has anyone else had success? This is the sample JSON to create an issues list and set the theme to a custom one I have in my tenant. I have been changing the version number as I made updates" { "$schema": "schema.json", "actions": [ { "verb": "createSPList", "listName": "Issue Tracking", "templateType": 1100, "subactions": [ { "verb": "SetDescription", "description": "List of Porject Issues" } ] }, { "verb": "applyTheme", "themeName": "Black n Blue" } ], "bindata": { }, "version": 1.2 }
