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

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

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

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. 

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.

@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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,484)