Forum Discussion
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.
1 Reply
Chad_V_Kealey Enterprise Content Types does indeed refer to out of the box content types and not content types you have created. However, I would highly suggest to not use the Content Type Hub all together as it as significant delays at scale, and they won't work well with your site designs and site scripts. If there is a scenario where you need centralized managed values in your columns, I would use the Managed Metadata Fields. Otherwise, I'd keep your content types on the site level and deployed through a Site Design.
The limit for Site Designs is 100 and the limit for Site Scripts is 100. This should be a large enough amount to account for most structures in an environment. Depending on your size, if you have more than 100, I may question the IA that is being put into place.
While technically, list templates are still available, this also requires turning noscript on and isn't recommended. These list templates also would not include any customizations such as PowerApps or Flow, though, neither does Site Designs and Site Scripts.
