Around 9 Modern Document LIbraries spread across 9 modern team sites. We use the default SharedDocuments library as this is the only one that has the full integration within Teams. These libraries have been renamed to "Department-Active Projects" Flow creates a series of subfolders inside various modern document sets across these libraries. All libraries have around 12 custom site columns which 10 are simply single line text and 2 are person coumn. Document sets are created using the standard document set content type. Folders are created using the new flow create folder action.
When flow executes to create the subfolders the following error occurs.
Hi @Dudditz ,
I have made a test on my side and the issue couldn't be reproduced on my side.
Please take a try with the "Create file" action to create the folder and then add a "Delete file" action to delete the file.
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello there, it does work using the create file action however this would add great length and complexity to the flow as there are quite a few folders used. I would prefer to use the Create folder action considering this is what it was specifically meant to do.
I just simulated the situation again, new site, new libraries, added 12 columns or so, problem exists. Created a new flow, Seems like a bug to me.
I believe we have isolated the issue. The create folder seems to fail often whenever the document set feature shared columns specifically when columns with spaces are selected. This however does not seem to be 100% of the time as one of the columns with spaces does work with the action however most others cause it to fail. It however does work when only columns that contain no spaces work as seen in the images. In all testing a new site was create with all new columns, no columns were ever renamed. This seems buggy and inconsistent in its behavior. Considering Document sets one would often want to create sub folders and one of the main reasons people often use Doc sets is for the shared column feature I would really like to see this work together as expected. A side not the create file action works fine which can create sub folders however not desirable if your creating lots of folders and also plumsail action works fine when creating subfolders with shared columns. So it seems to be specifically the new create folder action has the issue with modern doc sets shared columns. I have a ticket open with the SharePoint group and they seem uninterested and confused as to what I am showing them. Flow Fails on the left and works on the right.
This is a configuration of the document set, specifically the shared columns which I believe is where the issue is and causing the flows to fail.
I ran into the same issue and unfortunately am unable to resolve it due to the internal naming convention of the fields. However, I found a suitable workaround by using the Copy Folder Function. Here are the steps I completed:
Hi sfranchin thanks for the feedback. I guess your method is another work-around. It also seems to work when using the create file action however you than have to have followup actions to remove the folders. That said, I threw in the towel and learned how to create folders using send http requests which allows for the creation of many folders with less steps once you get the hang of it. Also, I have had a ticket open with Microsoft regarding the create folder action for several months and they have also been able to reproduce the issue and provide me weekly updates that the engineering team continues to look into it.
Obviously it's a bug and for those who work with document sets and shared columns its dead on arrival.
Fill out a quick form to claim your user group badge now!
We've given our badges an overhaul and also added some brand new ones!
Learn how to build the business apps that you need.
Find out where you can attend!
Watch & learn from the Power Automate Community Video Gallery!