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

Flow to assign documents to different people

Hi, I want to automatically complete the 'Assigned To' field when a document of a certain name is added to a sharepoint library and then notify that person.

Can anyone help please? 

1 ACCEPTED SOLUTION

Accepted Solutions

@STURNER Thanks for your patience on this!

Reporting here how we solved this flow.


In the condition, the "Name" item on the right frame was pointing to another column in the SPO library (probably also named "Name"). Changing it to the default library "Name" item made the condition work.

We also changed the trigger to "When a file is created" to avoid infinite loop.

View solution in original post

20 REPLIES 20
fchopo
Super User
Super User

Hello @STURNER 

In order to help you, you should provide more detailed information:

1) Which is the condition to be accomplished to trigger the flow? By file name?

2) Which task must be changed? Or the task should be created? (it doesn't exist).

3) Is the user who is uploading the file to SharePoint the one that has to be assigned to the task?

Regards,

Did I answer your question? Please consider to mark my post as a solution to help others.
Proud to be a Flownaut!

Thank you - answers below: 

1) Which is the condition to be accomplished to trigger the flow? By file name? 
Yes the file name would be the trigger as the file is being created through a document set so filename will always be the same

2) Which task must be changed? Or the task should be created? (it doesn't exist).
A new task would need to be created or just a notification sent to that user (chat in teams or email with link)

3) Is the user who is uploading the file to SharePoint the one that has to be assigned to the task?

No - a central administrator will create the document set which creates 10+ documents.  I then want a flow to assign the documents to relevant people (as unfortunately doc sets can't do that).  

Thanks

@STURNER Let's proceed step by step.

First of all, you can have your trigger use the file name as a condition by setting it like below:

 

1. For the trigger, choose a "When a file is created (properties only)" from SharePoint connector.

2. Set the site address and library name.

3. Open the trigger settings from [...] and add the "Trigger Condition" below:

       @equals(triggerBody()?['{Name}'], 'certainName') 

 

Replace "certainName" by the file name you want the flow to trigger at.

 

Please let me know if that helps and we'll move on to the next step. Thanks.

@JulienOlivier Hi, I have done that, can you help me now update the assigned to field with a specific person / group depending on document name and then send an email to them?  
Thanks so much in advance

Flow trigger.png

I have found that I can assign to a sharepoint group but not to an individual?  What syntax do I need to do that?

Thanks

@STURNER Here SharePoint groups are available in the dropdown selection, but you can also directly type individual (people in your tenant) account Email address. Or you can also enter it as dynamic content (click on "Enter custom value" for that).

 

Also, with the setting we made in the trigger, the flow will trigger only for one specific document name. So we cannot update the "Assign To" field depending on the document as it won't vary.

Else, we could remove that trigger setting to let the flow trigger each time a file is created. And then use a "Switch" that will update the "Assign To" field with a account Email address that depends on the document name.

 

Is it what you initially wanted to do?

@JulienOlivier  yes there are about 10 documents created as part of a document set and each one needs to be assigned to someone different so your suggestion of a switch sounds better but I don't know how to do that.  Can you help please?

@STURNER Ok, yes we can use a switch for that.

We can also create a dictionary that will store which file name belongs to which "Assigned To" account. That way it will be less cumbersome to do, I think. Let me explain how to do that below:

 

1. Add a "Compose" action and create a dictionary like below. I entered 2 sets but feel free to enter all your 10 sets.

(make sure to respect the syntax)

 

[
{
"fileName": "name1",
"assignedTo": "john@company.com"
},
{
"fileName": "name2",
"assignedTo": "bob@company.com"
}
]

JulienOlivier_0-1593638317386.png

 

2. Add a "Parse JSON" action.

In "Content", select the compose "Outputs" from dynamic content.

In "Schema", click on "Generate from sample", paste your whole dictionary and click "Done".

JulienOlivier_1-1593638570727.png

 

3. Add a "Condition".

At "Choose a value" on the left, pick "Parse JSON > fileName" in dynamic content (this will create an "Apply to each" frame).

Open the "Condition" action again.

At "Choose a value" on the right, pick "When a file is created (properties only) > Name" in dynamic content.

Then in the "If yes" frame, add an "SharePoint > Update file properties" action.

In the "Assigned To Claims", pick "Parse JSON > AssignedTo" from dynamic content. 

photo1.png

 

4. In the trigger settings, don't forget to remove the condition we created before.

 

That should be it. Give it a try and let me know if it worked as you expected!

 Hi, it runs ok i.e says the flow succeeded but it doesn't update the assigned to column and when I go into look at the run I get this;

 

STURNER_0-1593785466546.png

 

Hi @STURNER Thank you for trying.

The message that you got when you look at the run, is what should happen when you add a file in the library for which the file name is not in your dictionary. Could you double-check on that?

 

If you have a doubt, please post your dictionary and the file name here and I will take a look. Thanks.  

Here is my compose step;

[
{
"fileName": "1 Trustees Agenda",
"assignedTo": "taccount@blenheimpalace.com"
},
{
"fileName": "12 Date of next meeting",
"assignedTo": "taccount@blenheimpalace.com"
},
{
"fileName": "2 Draft minutes",
"assignedTo": "taccount@blenheimpalace.com"
},
{
"fileName": "3 Matters Arising",
"assignedTo": "taccount@blenheimpalace.com"
},
{
"fileName": "4 CEO Report",
"assignedTo": "taccount@blenheimpalace.com"
},
{
"fileName": "6 Strategic Land Update",
"assignedTo": "taccount@blenheimpalace.com"
}
]

 

Then in Parse JSON I hit Generate from sample and pasted the above into it - if you select Peek Code it looks like this;

 

{
    "inputs": {
        "content""@outputs('Compose')",
        "schema": {
            "type""array",
            "items": {
                "type""object",
                "properties": {
                    "fileName": {
                        "type""string"
                    },
                    "assignedTo": {
                        "type""string"
                    }
                },
                "required": [
                    "fileName",
                    "assignedTo"
                ]
            }
        }
    }
}
 
In the run history, it runs 7 times - once for the doc set folder and once for each of the 6 documents.
but using one of the runs which relates to a specific document you can see the output relates to one of the doc names in my dictionary
 
 

Annotation 2020-07-08 094011.png

 

 

 

 

@STURNER I don't see any problem in your Compose and Parse JSON steps. There are identical to mine.

In your run history, at Condition inside the "Apply to each", when upload your doc file to your library, you should have 5 "false" and 1 "true". Could you check on that?

 

Also, here is a screenshot of my flow that is working. Please compare it with yours.

I have set my Compose and Parse JSON steps identical to yours.

flow1.png

Hi

Thanks so much by the way for trying to help!  It is very much appreciated

In my run data, all 6 state False.  

STURNER_0-1594312394445.png

 

The only difference in my flow is that my initial trigger is When a File is created or modified (properties only) - could that be the issue?

Hi @STURNER 

Well, thanks for your patience too 🙂

 

No, the trigger that you use is not the cause.

There must be a problem in your condition. For some reasons, it's not satisfied.

Could you check its definition again?

 

It should be something like below.

JulienOlivier_0-1594332219351.png

If you happen to change an action or trigger that the condition is referring to, it may alter its definition.

 

Also, if you still meet this problem, could you paste a screenshot of the entire definition of your flow (with trigger and actions open)? I will take a look. Thank you.

 

step2.pngstep1.png

Hi @JulienOlivier sorry images posted the wrong way round but you will get the idea.  Does this help.  All looks OK to me?

@STURNER Thanks for your patience on this!

Reporting here how we solved this flow.


In the condition, the "Name" item on the right frame was pointing to another column in the SPO library (probably also named "Name"). Changing it to the default library "Name" item made the condition work.

We also changed the trigger to "When a file is created" to avoid infinite loop.

asmedic85
Frequent Visitor

Hello, 

 

I have a SharePoint list that I am using for tracking things. The form on the list is customized in PowerApps and both are working great. Now I want to take what I built a step further and add in automation. I have a report that has alot of the data that is currently being manually entered. I am going to build a flow to add list items to the SharePoint list but when they are added I want to assign them to certain employees based on the number of items currently assigned to that employee. In other words I am using this to evenly distribute workload. Is that do able using just Power Automate or will I need another program like access or something?

Hi there, 

I have been testing it out and for some reason i am stuck on Parse JSON. The error shows the following.

Compose:

 

[
{
"fileName": "name1",
"assignedTo": "abs@test.com"
}
]

 

Parse JSON:

aayub_0-1656008508815.png

{
    "type""object",
    "properties": {
        "inputs": {
            "type""array",
            "items": {
                "type""object",
                "properties": {
                    "fileName": {
                        "type""string"
                    },
                    "assignedTo": {
                        "type""string"
                    }
                },
                "required": [
                    "fileName",
                    "assignedTo"
                ]
            }
        }
    }
}
 
Error:
aayub_1-1656008744148.png

 

 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

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 (4,600)