cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Dudditz
Continued Contributor
Continued Contributor

Creating new folders inside Modern Document Sets - One or more field types are not installed properly

The scenario,

 

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.

 

"status": 400,
"message": "One or more field types are not installed properly. Go to the list settings page to delete these fields.\r\nclientRequestId: 1c3ad8b3-abff-4bc9-9157-bd50c389c757\r\nserviceRequestId: 1c3ad8b3-abff-4bc9-9157-bd50c389c757"
 
If you start deleting the various custom columns eventually it will start working however there is no consistancy in which ones need to be deleted.  For example sometimes if you delete 7 it will work, other times you have to delete all custom columns for it to start working, other times delete 3 it works, really makes no sense at all.  We have tested creating new modern sites all new libraries, all new custom columns, etc. and the issue just continues.  And once you add them all back its broken again or working for a while and than stops again with the errors.
 
We have been troubleshooting this for two weeks with no luck including a ticket open with Microsoft and no progress yet except providing some basic logs.  I am at a loss here, this is part of a very large integrated solution we are building for our ERP project Dynamics finance and operations that integrates sharepoint document mangement into Dynamics through the use of an integrated powerapp however without being able to create the subfolders within the document sets we are at a stand still.  I have included a screenshot of a very basic flow that fails.  If I create a new library, not the default shareddocuments library and attach the same flow to it, same columns, and same doc set content type it works most of the time or at least much more consistant than the default library however even new libraries start failing.  Any help or ideas is much appreciated.
 
PRJ-000659 in the photos is the document set.
1.jpg2.jpg
 
 
1 ACCEPTED SOLUTION

Accepted Solutions
Dudditz
Continued Contributor
Continued Contributor

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.

FailsFailsWorksWorks

View solution in original post

10 REPLIES 10
v-alzhan-msft
Community Support
Community Support

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.

 

Best regards,

Alice       

 

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.

Dudditz
Continued Contributor
Continued Contributor

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.

FailsFailsWorksWorks

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:

  1. Created a new document library named Folder Structure
  2. Added the desired folder structure I wanted added to new Document Sets
  3. Added ‘Copy Folders’ Action Step to Flow:
    • Current Site Address:   Current Site
    • Folder to Copy:   <Folder Structure Library>/<Folder>
    • Destination Site Address:   Current Site
    • Destination Folder:  <Document Library>/<Name - Name of Document Set>
    • If another folder is already there:  Fail this action
Dudditz
Continued Contributor
Continued Contributor

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. 

Hi Dudditz,

 

We are also struggling with this stupid behaviour and can confirm the following:

 

Create a folder in a library or a sub-folder - works

Create a folder in a doc set, no additional column - works

Create a folder in a doc set with additional columns, but these are not shared- works

Create a folder in a doc set with additional columns and these are shared- does not work

 

We would also open a case, since we need this functionality of sharing the column information of the folder and yes the behaviour literally screams for a bug or not designed for

I have had the exact same issue today and thanks to @Dudditz I at least have a clue now.

 

I think the spaces are the cause of the problem, but this can't be fixed by renaming your column to remove the spaces, you need to create a new column (without spaces of course).

 

If that messes up your naming convention, ironically, you can then rename the new column and put the spaces back in, and it will continue to work.

 

This is just in my limited experience and it may fail again, but the above seems to be working for me.

Spinner
Advocate IV
Advocate IV

I'm receiving the same error message with a custom content type based on Document Set. However, in my case, even removing every column (whether with a space or not) from the content type doesn't make a difference.

 

The flow works on normal folders, and on uncustomised Document Sets, but not on my custom content type.

 

Any advice welcomed.

Hi @Spinner 

 

It's a while since I did this so can't recall all the testing I did, but do your columns have any special characters in them other than spaces (i.e. underscores, dashes etc.)?  I wonder if it's special characters (not only but including spaces) that is the problem? 

 

Obviously when you create your column for the first time with special characters/spaces, but then rename them, it will still retain the original column name in the background (i.e. 'this column' renamed to 'thiscolumn', would still be called 'this_x0020_column'), hence my suggestion that all columns need to be created without them.

Spinner
Advocate IV
Advocate IV

Thanks for the reply @danbert1973 . No, there are no special characters in the names of the remaining columns of the list content type - I've stripped all columns out except for the standard Title, Name, and Description ones. I did have some columns whose names had spaces (and hence _x0020_ parts) but I removed all of them from the list content type (though they do remain in the site content type, which I can't readily modify, as it's used in production.)

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,708)