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

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