cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
N2P3
New Member

If SharePoint Folder create than create subfolder in the created folder

Hello everyone,

 

I have a challenge that I would like to solve automatically.

 

I would like that when I create a folder in a SharePoint document library (1st level), 5 subfolders (2nd level) automatically become in the created folder.

 

So I create a Vegetarian folder in the document library and the target screen should then look like this:

 

/Vegetarian
//Breakfast
//Brunch
//Lunch
//Teatime
//Dinner


Many thanks in advance and best regards
Nick

3 ACCEPTED SOLUTIONS

Accepted Solutions
ekarim2020
Super User
Super User

Here is a demo flow that should achieve the desired results:

Snag_239fe58a.png

1. THE TRIGGER

We start with the trigger When a file is created (properties only). Select the site and Library name:

Snag_23811636.png

We only want the flow to run if a new folder was created. We don't want the flow to trigger each time a new file is created. We can control when the flow runs or triggers by using a trigger condition:

Snag_23815cc5.png

Select Settings:

Snag_2381a3e0.png

Click add, then add the trigger condition:

Snag_2381f173.png

The flow will only trigger if a folder was created. You can copy-and-paste the following text into the Trigger Conditions:

 

 

 

 

@triggerOutputs()?['body/{IsFolder}']

 

 

 

 

Snag_2db424e0.png

 

2. THE LIST OF SUBFOLDER NAMES

Initialize an array variable to store the list of subfolder names that need to be created:

Snag_23867e6e.png

3. GET PATH UNDER WHICH SUBFOLDERS ARE TO BE CREATED

Use a compose variable to store the folder path under which the subfolders should be created. The path needs to be in the format: [Document Library name] / [New Folder Name].

 

You can copy-and-paste the following text into the Inputs of the Compose action:

 

 

 

 

@{first(split(triggerOutputs()?['body/{Path}'],'/'))}/@{triggerOutputs()?['body/{Name}']}

 

 

 

 

Snag_238afd9d.png

The full path looks something like this for a Document library called Lib1 and a new folder called Folder2: Lib1/Folder2 .

 

We split this text (Lib1/Folder2) at the '/' character then take the first part of the string which is Lib1, the name of the Document Library.  We then add / character followed by the new folder name. This compose variable holds path to where we expect the new folder to have been created i.e. under the root of the document library.  We will check to see if the folder was indeed created under the root of the document library in the next step.

 

4. CHECK THAT THE NEW FOLDER WAS CREATED UNDER THE ROOT

Add a condition action. We will check to see if the new folder (which triggered the flow) was created under the root of the document library.

Snag_2391e502.png

 

If the new folder was created under the root of the document library, then create the sub folders "Breakfast",
"Brunch","Lunch","Teatime" and "Dinner"

Snag_23972416.png

Snag_239c5280.png

You can paste the following directly into the Folder Path:

 

 

 

 

@{triggerOutputs()?['body/{Name}']}/@{items('Apply_to_each')}

 

 

 

 

Here is some sample runtime output:

Snag_23ad74fa.png

Hope this helps.


Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

Hi @SPOLHE-C and @Timmay313 ,

 

Here is an updated version of the flow that I never posted. It is much simpler than the previous version:

ekarim2020_3-1651871649689.png

 

1. THE TRIGGER

We start with the trigger When a file is created (properties only). Select the site and Library name:

Snag_1046025a.png

The flow uses two trigger condutions for the When a file is created (properties only). We only want the flow to run if:

  1. A new folder was created,
  2. The folder was created under the root of the document library. 

We don't want the flow to trigger each time a new file is created and we don't want the flow to trigger each time a new folder is created that was NOT created under the root of the document library. We will control when the flow runs or triggers by using two trigger conditions:

Snag_1046332e.png

 

@triggerOutputs()?['body/{IsFolder}']
@equals(length(split(triggerOutputs()?['body/{FullPath}'],'/')),2)

 

The second trigger condition is used to detect if a folder was created under the root. The split function is used to  split the FullPath prorerty. FullPath is where the new folder was just created. We split the FullPath at the '/' character, then we count, using the length() function, how many elements the split() function produced. A value of 2 means that the folder was created under the root of the document library:

 

Snag_12dadffe.png

This trigger condition should prevent the flow from triggering itself again when the flow creates the subfolders "Breakfast", "Brunch", "Lunch", "Teatime" and "Dinner". The flow should only trigger if a folder was created under the root of the document library. 

 

2. THE LIST OF SUBFOLDER NAMES

Initialize an array variable to store the list of subfolder names that need to be created:

Snag_105a28eb.png

3. APPLY TO EACH LOOP - TO CREATE EACH SUBFOLDER

The subfolders will be created under the new Folder that triggered the flow in the When a file is created (properties only) action. The subfolders will be created using the path Folder Name/Subfolder Name:

Snag_10736a6f.png

Snag_1074a1e6.png

 

Here is a sample runtime output:

Snag_107de396.png

Hope this helps.

 

Ellis

View solution in original post

Hi @David6010 ,

 

Add a third trigger action so that the flow only triggers if the newly created folder has a folder path that contains 'Shared Documents/Share Area/DMcK'  . See trigger (3) below for an example:

ekarim2020_2-1657536532782.png

 

Your create action would be similar to the screen below:

ekarim2020_3-1657536628263.png

 

Name property contains the name of the new folder that triggered the flow.

 

Hope this helps.


Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

47 REPLIES 47
ekarim2020
Super User
Super User

Yes, this should be possible.

 

The logic of the flow will resemble something like this:

ekarim2020_0-1641322943676.png

 

Was the object created in SharePoint a File or Folder?

Was the Folder created under the root of the Document Library?

I'll try to post a flow demo later.

 

Ellis

ekarim2020
Super User
Super User

Here is a demo flow that should achieve the desired results:

Snag_239fe58a.png

1. THE TRIGGER

We start with the trigger When a file is created (properties only). Select the site and Library name:

Snag_23811636.png

We only want the flow to run if a new folder was created. We don't want the flow to trigger each time a new file is created. We can control when the flow runs or triggers by using a trigger condition:

Snag_23815cc5.png

Select Settings:

Snag_2381a3e0.png

Click add, then add the trigger condition:

Snag_2381f173.png

The flow will only trigger if a folder was created. You can copy-and-paste the following text into the Trigger Conditions:

 

 

 

 

@triggerOutputs()?['body/{IsFolder}']

 

 

 

 

Snag_2db424e0.png

 

2. THE LIST OF SUBFOLDER NAMES

Initialize an array variable to store the list of subfolder names that need to be created:

Snag_23867e6e.png

3. GET PATH UNDER WHICH SUBFOLDERS ARE TO BE CREATED

Use a compose variable to store the folder path under which the subfolders should be created. The path needs to be in the format: [Document Library name] / [New Folder Name].

 

You can copy-and-paste the following text into the Inputs of the Compose action:

 

 

 

 

@{first(split(triggerOutputs()?['body/{Path}'],'/'))}/@{triggerOutputs()?['body/{Name}']}

 

 

 

 

Snag_238afd9d.png

The full path looks something like this for a Document library called Lib1 and a new folder called Folder2: Lib1/Folder2 .

 

We split this text (Lib1/Folder2) at the '/' character then take the first part of the string which is Lib1, the name of the Document Library.  We then add / character followed by the new folder name. This compose variable holds path to where we expect the new folder to have been created i.e. under the root of the document library.  We will check to see if the folder was indeed created under the root of the document library in the next step.

 

4. CHECK THAT THE NEW FOLDER WAS CREATED UNDER THE ROOT

Add a condition action. We will check to see if the new folder (which triggered the flow) was created under the root of the document library.

Snag_2391e502.png

 

If the new folder was created under the root of the document library, then create the sub folders "Breakfast",
"Brunch","Lunch","Teatime" and "Dinner"

Snag_23972416.png

Snag_239c5280.png

You can paste the following directly into the Folder Path:

 

 

 

 

@{triggerOutputs()?['body/{Name}']}/@{items('Apply_to_each')}

 

 

 

 

Here is some sample runtime output:

Snag_23ad74fa.png

Hope this helps.


Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

N2P3
New Member

Thank you very much!

I would like something like this but to trigger under the 2nd level or a subfolder. Parent Folder>Subfolder2<Populate this subfolder with the 5 folders. I have it set up just cant connect the path back to the subfolder2. 

Timmay313
Helper I
Helper I

Maybe something changed since this was posted, can't seem to get it to work through. It triggers and creates the new folders but created them in <Library>/<Library>/Folder/subfolder. creating a new folder named the same as the document library.

SPOLHE-C
Frequent Visitor

I've been getting a lot of errors on previously stable flows the past couple of weeks, so was pleasantly surprised when this didn't fail--but it also didn't create the subfolders. Run history shows the Apply to each as "skipped." Which is new to me!

Apply to each-skipped 2022-05-06.png

Any suggestions would be appreciated.

@SPOLHE-C  and @Timmay313 

Luckily I still have a version of this flow. I tested it and it is still working.

 

Here the flow succeeded, as a folder was created under the root directory:

ekarim2020_1-1651858518400.png

 

The skipped actions are due to a new folder being created, but it was not created under the root folder, so the flow doesn't need to take any further action. However, the flow also will be triggered by the flow itself(!) when creating the subfolders "Breakfast""Brunch",  "Lunch",  "Teatime"  and "Dinner" - as the flow triggers each time a folder is created. However, as these folders are not created under the root folder, the condition check will be false so the  flow doesn't need to take any further action and so will skip the Apply to each loop:

ekarim2020_0-1651858394103.png

The runtime output of the flow showing that the flow is being triggered by the flow itself when it creates each of the subfolders:

Snag_fcac680.png

You can add a compose action to see what is going on:

Snag_fc13b14.png

 

The sub folders will only be created if the SubFolderPath = Full Path.

 

Hope this helps.


Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

Created as a folder directly beneath the library without sub-folders, and, yes, that works. I can get your inputs = false and Apply to each = skipped from here by adding a level, so you are correct about the reason for the earlier failure, and I shall mark this as solved. Now off to figure out an automated move to go with that delay-then-copy-file code block that used to work...  

successful subfolders flow 2022-05-06.png

Hi @SPOLHE-C and @Timmay313 ,

 

Here is an updated version of the flow that I never posted. It is much simpler than the previous version:

ekarim2020_3-1651871649689.png

 

1. THE TRIGGER

We start with the trigger When a file is created (properties only). Select the site and Library name:

Snag_1046025a.png

The flow uses two trigger condutions for the When a file is created (properties only). We only want the flow to run if:

  1. A new folder was created,
  2. The folder was created under the root of the document library. 

We don't want the flow to trigger each time a new file is created and we don't want the flow to trigger each time a new folder is created that was NOT created under the root of the document library. We will control when the flow runs or triggers by using two trigger conditions:

Snag_1046332e.png

 

@triggerOutputs()?['body/{IsFolder}']
@equals(length(split(triggerOutputs()?['body/{FullPath}'],'/')),2)

 

The second trigger condition is used to detect if a folder was created under the root. The split function is used to  split the FullPath prorerty. FullPath is where the new folder was just created. We split the FullPath at the '/' character, then we count, using the length() function, how many elements the split() function produced. A value of 2 means that the folder was created under the root of the document library:

 

Snag_12dadffe.png

This trigger condition should prevent the flow from triggering itself again when the flow creates the subfolders "Breakfast", "Brunch", "Lunch", "Teatime" and "Dinner". The flow should only trigger if a folder was created under the root of the document library. 

 

2. THE LIST OF SUBFOLDER NAMES

Initialize an array variable to store the list of subfolder names that need to be created:

Snag_105a28eb.png

3. APPLY TO EACH LOOP - TO CREATE EACH SUBFOLDER

The subfolders will be created under the new Folder that triggered the flow in the When a file is created (properties only) action. The subfolders will be created using the path Folder Name/Subfolder Name:

Snag_10736a6f.png

Snag_1074a1e6.png

 

Here is a sample runtime output:

Snag_107de396.png

Hope this helps.

 

Ellis

That is simpler, doesn't accomplish what I am trying to do though. We use Teams along with SharePoint so all the sites are setup with the structure <Library>/<teams Channel>/<subfolders>. This allows the creation of subfolders within document library but not within the teams channel folders. 

 

Is it possible to create the array of folders when a folder is create in the 3rd level of the structure? 

Here is what i tried to do:

Timmay313_5-1652112050047.png

 

Timmay313_2-1652111535307.png

Timmay313_4-1652111616516.png

 

This triggers when a new folder is created in the 3rd level, DocLib/Channel/Folder/ but will recreate the folder as DocLib/Folder/subfolders.

Triggered by creation of this folder 

Timmay313_6-1652112100119.png

This is the output i get from the flow running. 

Timmay313_8-1652112152692.png

 

Try the following and let me know how you get on:

Snag_40735af.png

 

Snag_404fdc0.png

 

Snag_406609c.png

Hope this helps.

 

Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

Well, it didnt like the 3rd condition added to the trigger settings. removed that and left the rest. it ran and added subfolders to the trigger folder.

Thanks Ekarim2020,

 

It solved my solution Thank lot. Only problem I am seeing its taking 30 seconds to 50 seconds to create sub folders, I am creating just 5 folders. But it taking time. Any solution bro please advise.

 

Thanks

Jameel

Hi @jameela1 ,

 

30 -50 seconds is actually very responsive! A wait time is to be expected due to the nature of cloud services; it will never be instant. In my development environment the flow took about 50 seconds before it was triggered.

 

You can see how often this flow is configured to trigger by Microsoft:

Snag_3f91dc6.png

Snag_3f963c8.png

In the above case, the flow is triggered to run every 3 minutes.  Therefore, sometimes you may need to wait for up to three minutes before the flow triggered again - but there are other always factors involved too.  Your licensing plan for Power Automate will affect how frequently flows triggered along with other limits or entitlements. See Microsoft Power Apps, Microsoft Power Automate and Microsoft Power Virtual Agents Licensing Guide (P... 

 

Ellis

 

 

ok I understand, Thanks for your quick reply.

MathewM
Helper I
Helper I

@ekarim2020 

 

Thank you very much for such a detailed breakdown on this process, it works perfectly and saved me a bunch of time trying to figured how to check if a folder was created under the root.

Hi @ekarim2020

 

I have doubt what is the syntex for creating multilevel sub folders for example you are creating 5 folders in that first one is Breakfast in side that folder i need to create two sub folders like "Coffee", "Tea", in that what is the syntex for array. Please advise.

 

Thanks

HI @jameela1 ,

 

Just add any subfolders to the array using the following format:

 

[
"Breakfast",

"Breakfast/Coffee",

"Breakfast/Coffee/Nestle",

"Breakfast/Tea",

"Brunch",
"Lunch",
"Teatime",
"Dinner"
]

 

Note that if you only had the following path in the array:

"Breakfast/Coffee/Nestle"

 

SharePoint would create Breasfast, Coffee and Nestle folders in one action.

 

So in theory you could just have:

[

"Breakfast/Coffee/Nestle",

"Breakfast/Tea",

"Brunch",
"Lunch",
"Teatime",
"Dinner"
]

 

But the first array example may be far more readable.

 

Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

Thanks @ekarim2020 This is working perfectly..Thanks lot!!!

 

Is there is any possibility to setup security for example folder "Breakfast" should be access by Peter or GroupMembers other should not permit. Please advise.

 

Thanks

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,300)