Forum Discussion
Praveen_Battula
Sep 23, 2019Copper Contributor
Best practice for provisioning content types in modern team sites
We have a requirement to provision sites using a form we are building in SPFX web part to restrict who can create specific sites. This process requires lot of inputs from user to provision site and s...
Gregory Frick
Sep 26, 2019Iron Contributor
Praveen_Battula - The Content Type Hub has always been a great idea, but the variation in replication times is very frustrating. I think you can create content types using the Same ID, but you'll have to test it and it should be fairly easy to setup a test like that. Choose a content type that you already have on the CT Hub and create it with the same id on a test site. Then check the Content Type Publishing error log for errors ( _layouts/15/contenttypesyndicationhubs.aspx ). You may have to wait awhile. Good Luck
Praveen_Battula
Sep 26, 2019Copper Contributor
Thanks Gregory Frick.
I have tried them and used same content type Id and site fields and fieldref in content types. But I do see the error messages in content type publishing error log as conflicts. But this conflict error message only gets for few content types not to all content types.
So I am not sure what is the best practice here to implement these kind of requirements with modern sharepoint.
At the moment we have implemented azure automation runbook which waits till content types available and then finish post provisiong steps. Sometime we see 1 hr to 2 hr to show up content types. We are unnecessarily paying for runtime in azure, also customers are waiting for hours to show up site for use. I feel like there must be better solution to make things simple.
-Praveen.
I have tried them and used same content type Id and site fields and fieldref in content types. But I do see the error messages in content type publishing error log as conflicts. But this conflict error message only gets for few content types not to all content types.
So I am not sure what is the best practice here to implement these kind of requirements with modern sharepoint.
At the moment we have implemented azure automation runbook which waits till content types available and then finish post provisiong steps. Sometime we see 1 hr to 2 hr to show up content types. We are unnecessarily paying for runtime in azure, also customers are waiting for hours to show up site for use. I feel like there must be better solution to make things simple.
-Praveen.
- JimmyWorkNov 25, 2019Iron Contributor
Im having the same issue myself.
I just put a delay in the Flow using the delay trigger.
I would like to know if possible how you check when content types are available?