cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
mdemarici
Frequent Visitor

Move files from my companies SharePoint Site to our clients site based on metadata tags.

My objective is to be able to upload a document in our document library, tag it with metadata including the client's name, doc type, etc. and have it automatically move to our client's site based on the tags. I think this can be done with a flow, but I am concerned that our folder structure will get in the way. 

 

Currently, our Doc Library and Clients Site's Doc Library is set up with a multi-level folder structure. There are about 400 folders in our library and about 100 in our clients sites. Would it be better to have a flat structure in order to perform this automation?

 

A visual of my companies and our client's folder structure

 

Folder 1 - Microsoft

Folder 2 - Apple

Folder 3 - AMD

Folder 4 - XYZ

 

inside of each of these folders are subfolders...

 

Folder 1 - Legal

Folder 2 - Financial

Folder 3 - Reports

Folder 4 - Transactions

 

Inside each of these folders are folders that correspond with the year. 

 

This would be the ideal scenario if everything worked correctly...

 

I (Marcus) receive documents for my clients, Daniel and Chris from a company that we both deal with, let's call it Microsoft. I download the files and navigate to the Microsoft Company folder then to the financial documents subfolder then to then 2020 folder. I drag the files into the window to upload them, hit quick edit, and tag each file with Metadata (clients name, doc type, etc). Once I am done tagging, an automated flow moves Chris's file to his SharePoint site and Mike's to his. Chris and Mike can only see documents tagged with their names, and they can also see that the document is in their Microsoft folder in the Financial Documents subfolder. 

 

Is this possible with multi-level folders? It is to my understanding I would have to map the target folder to the source folder, doing this would take a lot of time considering there are about 5 subfolders in each Company folder. Would it be better if I was working with a flat structure with only metadata columns?

 

My company and my clients are used to using the folders, I would like to figure out a way where I can keep the folder structure, but I'm unsure whether I have to map each folder or if there is a better way to handle this.  I can potentially convince management and clients to switch to a flat structure if I can make it have a similar look and feel, navigation, etc. 

 

Thank you for reading!!

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @mdemarici 

Thank you for the information. Let me try and make it clearer.

I use a string variable to build the folder path, so after your trigger, initialize a variable to hold the folder path - initial value usually is the document library. See my screenshots below. I have included only the parts where I ensure that the folder path in which the document is to be moved, exists before the move file action.

MoveFileToTargetACustomer.png 

First part is to get the customer value from the file properties and add it to my folder path variable (TargetPath).

I then check to see if the folder exists already and if it does, I just continue, but if it does not exist then I create it.

 

The same I do with the file property Service ... add to variable, check that folder exists, create if not.

MoveFileToTargetBService.png

Do the same for all your properties/folder levels 😉

At last just use a Move file action to move your file from its path to the folder path variable.

Kind regards, John

View solution in original post

10 REPLIES 10
JohnAageAnderse
Memorable Member
Memorable Member

Hello @mdemarici 

I can't decide for you what you and your partners will do, but I can give a little information on how we are using Flow to move our documents around and the reason for it. Please note that we mostly are using Classic SharePoint still 🙂

 

In the beginning we had the Shared Documents library as a flat structure, no folders at all. At the same time we have a lot of different customers for which we need to have specific documentation. We were forced to include the customer name in the documents filename, so as not to have a conflict on naming.

 

We had already added several properties to the documents library - customer, service, tags. Also several content types were defined. As our colleagues works in teams and each teams provides support for one or more services, the above allowed us to create team pages and team customer pages which presented their customers and the documents related to customers and services - we introduced a minimal click solution for our teams - 1st click on customer, 2nd click on the document.

 

After some time, to avoid the filename conflict, we decided to introduce folders in the document library. We went with 3 levels, customer, service, content type. The introduction of folders had no impact on the presention in the team customer pages.

 

A flow was setup to automatically move a document into the correct folder based on the properties. By now having documents inside this folder structure, our colleagues can now name their documents without a customer name.

 

Hope the above gives you some ideas. Kind regards, John

Hi John, 

 

Thank you for taking the time to reply. I was able to get a flow going that moves the documents to a folder based on tags, any tips on moving the files to sub folders?

 

It sounds like our situations are similar. Us and our clients receive documents from a fairly large number of other companies. This semi large number of company names would be the names of the sub-folders. Do you have any insight as to how to write the flow to go to sub-folders? Do I have to write a condition for each company, or is there a way to do it with fewer conditions?

 

right now my flow is like this 

 

get created doc --> pull metadata --> if client abc, move to client abc folder 

 

What would be the best way to do this..

 

get created doc --> pull metadata --> if client abc, move to client abc folder --> move to company name folder within client abc folder

 

Thanks again for the help! @JohnAageAnderse 

Hello @mdemarici 

We use a known folder structure, so even when a new customer comes in or they start to receive a service, the flow will automatically create the needed folder structure.

The flow starts by building the folder path - first as just the customer name, checks that the folder exists, creates it if not - then takes the next level from the properties - service, adds it to the folder path, checks that the folder exists, creates it if not - and so on.

A document can end up in either the customer folder, the service folder or in the content type folder. The reason some documents ends up in the customer folder, is that they are not related to a service.

My best suggestion is for you to discuss your needed structure with your colleagues and then implement a solution for it.

Kind regards, John

Thank you, John. That description was very helpful to me!

Hi @JohnAageAnderse I'm trying to mimic your description, but I am unsuccessful. would you mind sending me a screenshot of how the flow starts by building the path?

 

Do you use the "create a new folder"  process?

Hello @mdemarici 

Thank you for the information. Let me try and make it clearer.

I use a string variable to build the folder path, so after your trigger, initialize a variable to hold the folder path - initial value usually is the document library. See my screenshots below. I have included only the parts where I ensure that the folder path in which the document is to be moved, exists before the move file action.

MoveFileToTargetACustomer.png 

First part is to get the customer value from the file properties and add it to my folder path variable (TargetPath).

I then check to see if the folder exists already and if it does, I just continue, but if it does not exist then I create it.

 

The same I do with the file property Service ... add to variable, check that folder exists, create if not.

MoveFileToTargetBService.png

Do the same for all your properties/folder levels 😉

At last just use a Move file action to move your file from its path to the folder path variable.

Kind regards, John

Hi @JohnAageAnderse 

Thank you for your continued support in this.

 

One quick question on the creation of the folder using the folder path string variable.

 

I'm getting an error that the folder name contains characters that are not supported when I use the folder path target variable in the create new folder step. Pic below. is there another way to use that variable in the create folder step so that it works?

 

 I also noticed in your pictures earlier, you used the get folder metadata using path step, I tried that and was also getting some errors as the target path was "not found" and for some reason, it didn't move onto the next step even when the "run after" said to move on whether it succeeds or fails

 

to understand this correctly, the target path is where the document needs to be added, the destination aka the customer folder, correct? if so, if it's not created yet, is the "get Folder metadata from the target path" step going to automatically fail, and that's why you have the "run after" step?

 

Thank you so much again, your last reply was a breakthrough for me and I feel like I am very close to solving this now. 

 

 

Hello @mdemarici 

Good to see that you are moving forward 🙂

 

About the folder path - yes, it must not contains any unsupported characters - you will have to look up what they are. I do change one character due to us having danish customers also and their name may have a slash "/" in it (a company type "A/S"), so we decided to just remove it.

 

The reason we are checking for the existence of a folder is that the customer may be new, or the service may be newly signed up to, so the folder may not yet exist.

 

By the way, in your condition it says "TargetPath contains TargetPath"?? It should be "<get folder meta data using path>Id is not equal to null (expression)" - testing if the action returned anything (old solution before Configure run after became available).

Kind regards, John

Thanks! @JohnAageAnderse 

 

Thanks for the clarification, so I have to change the characters inside the variable itself, the fact that im putting the variable in the folder path box isn't the issue? 

 

The if TargetPath contains TargetPath is actually TargetPath contains TargetPath2. I ended up making another variable that didn't have the customer name as a folder at the end because I was not sure why I was getting the error on the "Get folder Metadata using path" Step. it was saying it didn't exist. 

Was I running that step correctly? I was using the target path as the folder for the step. 

 

Thanks!

Hello @mdemarici 

The step Get folder metadata using path may succeed or may fail - the condition after checks to see if it was a success (Yes branch) or a failure (No branch).

Today with the features available, you actually don't need the condition, but can use a scope to hold the No branch steps and then configure the Scope to run only after a failure in the Get folder metadata using path step. (A future task for me to update our flow).

Kind regards, John

Helpful resources

Announcements

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. Our team will be reviewing posts using the new "Copilot" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!    

Tuesday Tips: Getting Started in the Community

TUESDAY TIPS is back!   This weekly series of posts is our way of sharing helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! The original run of Tuesday Tips was a highlight of last year, and these all-new Tips will hopefully prove to be just as informative as helpful. We will cover some basics about the Community, a few "insider tips" to make your experience even better, and sharing best practices gleaned from our most active community members and Super Users. Make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   THIS WEEK: I'm Brand New! What Do I Do? The number of new community members we have each week is pretty amazing, and we are so glad to welcome all of you to the Community! You may be wondering. "What do I do? Where do I get started? Will anyone be willing to help me? What I have a question? Help!"   Let's start with this: Welcome to the low-code revolution, and more importantly, welcome to the Power Platform Community! This is a great place to start. Whether you're busy with Power Apps, getting familiar with Power Automate, engaging Copilot Studio, or building in Power Pages, there are a few key places you should check out as you begin your journey: FORUMS: The forums are THE place to ask questions, look at questions asked by other Community members—and see answers and solutions from our Super Users and other helpful people in the Community. Power Apps ForumsPower Automate ForumsCopilot Studio ForumsPower Pages Forums   NEWS & ANNOUNCEMENTS: Our News & Announcements section highlights the newest and greatest updates in the Community, news from the product team, and so much more. It’s updated a few times each week and will also help you find ways to connect with what’s going on in the ever-growing world of Power Platform. Power Apps News & AnnouncementsPower Automate News & AnnouncementsCopilot Studio News & AnnouncementsPower Pages News & Announcements   GALLERIES: The Galleries section of the Community features tons of tips and tricks, features and benefits, and more—through videos created by our Super Users, product teams, and other helpful members of the Community. Power Apps GalleriesPower Automate Galleries Copilot Studio GalleriesPower Pages Galleries BLOGS: The community blogs section is full of handy step-by-step tips from members of the Community—and some of them include detailed answers to some of the questions most frequently asked questions, as well as how they solved a problem they faced. Power Apps Community BlogPower Automate Community BlogCopilot Studio Community BlogPower Pages Community Blog POWER UP PROGRAM: If you’d like to really take a huge step forward in your journey, we recommend checking out the Power Up Program, a Microsoft-sponsored initiative that trains new Power Platform users and has been a huge success since it launched a little over a year ago. There’s a waiting list, so definitely apply soon if you’re interested! Find out more here: Microsoft Power Up Program for career switchers.   There's so much more you'll discover in your Power Platform experience, and this Community is here for YOU! We are glad you've discovered us and can't wait to see where you grow! If you're new to the Community and just getting started, make sure to give this post a kudo and introduce yourself so we can welcome you!

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Microsoft Power Platform | 2024 Release Wave 1 Plan

Check out the latest Microsoft Power Platform release plans for 2024!   We have a whole host of exciting new features to help you be more productive, enhance delegation, run automated testing, build responsive pages, and so much more.    Click the links below to see not only our forthcoming releases, but to also try out some of the new features that have recently been released to market across:     Power Apps  Power Automate  Copilot Studio   We can’t wait to share with you all the upcoming releases that will help take your Power Platform experience to the next level!    Check out the entire Release Wave: Power Platform Complete Release Planner 

It's Time to S.U.I.T. Up! Season One Begins This Week

        After its initial announcement met with such resounding success at the Microsoft Power Platform Conference last fall, the Super User In Training Program's first season is about to kick off! We are so excited to welcome hundreds of potential new Super Users who have signed up for our inaugural program.Not sure what a Super User is yet? Keep reading:Have you ever been exploring the community and come across a user with this unique icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they are consistently helpful with everything from solutions to flagging spam, offering insight on the community, and so much more!If you've ever wondered exactly what a Super User does and how they earn that special badge, please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Virtual Agents: What is A Super User? - Power Platform Community Power Automate: What is A Super User? - Power Platform CommunityPower Pages: What is A Super User? - Power Platform CommunityIf you missed this season of S.U.I.T., don't worry! We have a whole new season coming soon, so watch our News & Announcements for updates on when you can sign up and get your Super User SUIT on!

Users online (4,188)