Power Automate Create sites scripts, designs, and archive for later use

 This step is part of the longer post 

Duplicate Sharepoint Online Subsite with all Site Contents and Page[s] - Power Automate

And therefor was moved to a seperated post.



3. Create sites scripts, designs, and archive

This is a 1-time process (for each design), so it should live as a manually triggered flow. Whenever you make a change, you need to run this again (and change what is relevant, if needed).
REMEMBER - that will only affect newly created subsites, not old ones!

I will show 1 Flow for 1 template, and you should create multiple, 1 for each template

This is the full flow, and I will explain each piece



Steps 1-3: 

1 - Trigger, nothing to it,
2 - Initialize Variable type of Array, to store the array of our lists and libraries to be copied
3 - Get all lists, retrieve all Custom Lists and Document Libraries Display Names, from the Template Site (in my example - "ITX2-root")



NOTICE - this is problematic in 2 ways:
First it retrieves only the Display Names, meaning that in the following scenarios you will get bad results as we need the Internal Names:
A. you changes the name
B. you created the lists/libs not in english letters (Hebrew ect.)

Second you only get 2 types - Custom Lists (100) and Document Libraries (101). If you need more lists like Calendars and other defaults you cant get them like this.

The solution for both of these problems is to use HTTP step for /_api/web/lists and then you need to smartly filter that ect., its more messy and require more work and wont be covered here.



Step 4 - Apply to Each


We need to 1st decide who is a list (type 100) and who is a library (type 101) since we need to add the "/Lists" prefix to the lists

A simple condition but we must write the expressions ourselves since the Dynamic Content doesnt show the "Type" property

So add a Condition, click "Name" for example from the get all lists step and fix it
Final value (for me) is items('Apply_to_each')?['Type']
For the right-hand side just string(100)


If Yes, its a list, lets add it to our variable with the prefix
concat('Lists/', items('Apply_to_each')?['DisplayName'])
Notice - no starting slash (/)
If you are using another api, you need to put the list actual url (i.e. internal name)




If No, its a Document Library, and we need another condition since the Display Name of the default DocLib is always changed, "Documents" for English, and whatever for your language, so you need to handle those cases and set the value to "Shared%20Documents"

So another Condition, test for the above 2 values, for our default we add 
concat('', 'Shared%20Documents') 
and for others 
concat('', items('Apply_to_each')?['DisplayName'])
(and yes you can remove the concat, but I just copy-pasted)
MAKE SURE THE CONDITION IS OR





Steps 5-7:

5 - Compose the Variable

6 - Get Site Script - its a "Send an HTTP request to SharePoint" action step, and lets detail it:

a. The site address is not important as it is saves globally
b. POST method
c. /_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.GetSiteScriptFromWeb
d.   Accept      +         application/json;odata=verbose
e. The body of GetSiteScriptFromWeb endpoint can be adjusted a bit if needed as documented here. Make sure you change the webUrl to your webUrl

{"webUrl":"https://bresleveloper.sharepoint.com/sites/ITX2-root",
"info":{
"IncludeBranding":true,
"IncludedLists":@{outputs('Compose')},
"IncludeRegionalSettings":true,
"IncludeSiteExternalSharingCapability":true,
"IncludeTheme":true,
"IncludeLinksToExportedItems":true}}


7 - Parse the JSON property from the results. 
outputs('Get_Site_Script')?['body']?['d']?['GetSiteScriptFromWeb']?['JSON']
Use {} for the schema since we dont need it detailed







Step 8 - Create New Site Script

This will create a SiteScript that includes all the lists and libs needed to be added and with all their columns (and formatting). You should take a look the the "Raw Output" of the "Parse JSON" action step. We will put it the the Site Design step that can include more than 1 script.

Its a "Send an HTTP request to SharePoint" action step, and lets detail it:
The site address is not important as it is saves globally
Uri is (Make Sure to change the @title value to your end)

/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.CreateSiteScript(Title=@title)?@title='ITX2-Script'

Headers : 

Accept              application/json; odata.metadata=minimal
Content-Type        application/json;charset=utf-8
x-requestdigest     _spPageContextInfo.formDigestValue
ODATA-VERSION       4.0

And the body is the value parsed for the "Parse JSON" action step




Step 8 - Create New Site Design

Its a "Send an HTTP request to SharePoint" action step, and lets detail it:
The site address is not important as it is saves globally
Uri is (Make Sure to change the @title value to your end)

/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.CreateSiteDesign

Headers : 

Accept              application/json; odata=verbose

And the body includes the ID of the SiteScript from the above step (Make Sute to change the Title and Description to you end)

{
  "info":{
    "Title":"ITX2-Design",
    "Description":"SubSite Example Test with lists libs files items",
    "SiteScriptIds":["@{body('Create_New_Site_Script')?['Id']}"],
    "WebTemplate":"1",
    "PreviewImageUrl": "",
    "PreviewImageAltText": "Customer tracking site design theme"
  }
}







Step 10 - Archive in helper list

This action is actually Create Item. To further inspect the Archive Helper list I created visit the main post

Here the Site Address IS important and needs to match the helper site.
Just copy-paste your titles and the script ID.
For the template id use:
body('Create_New_Site_Design')?['d']?['CreateSiteDesign']?['Id']






Best advise is to manually test it and use the correct data from the archive helper list whenver needed.
If you prefer there are examples out-there of how to make all this via O365-PowerShell


Best of Luck








Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab...
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX ...
Read more