cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AMH08
Advocate I
Advocate I

Approval Process Requested By

We have a centralized flow account to manage some business Flows. 

 

I find myself tinkering with an approval flow. The approval is working. However, the approval always says it is being requested by the account the flow lives on. Is there a way to configure that to be someone else without the flow living on that someone else's account? 


What I would like to do is have the requested by be whoever was entered in a person field within the sharepoint list item that was triggered by the flow. 

 

The only options I see for the approval is:

Title, Assigned To, Details, Item Link, Item Link Description. 

29 REPLIES 29
v-xida-msft
Community Support
Community Support

Hi @AMH08,

 

Do you want to change the requestor (Requested by) of the Approval email sent through "Start an approval" action dynamically?

 

The requestor (Requested by) of the approval email sent through "Start an approval" action is based on your current login account of Microsoft Flow. In other words, if you login in Microsoft Flow with the account of user A, the requestor (Requested by) of the approval email sent through "Start an approval" action is user A, if you login in Microsoft Flow with the account of user B, the requestor (Requested by) of the approval email sent through "Start an approval" action is user B.

 

There is no way to change the requestor (Requested by) of the Approval email sent through "Start an approval" action dynamically in Microsoft Flow currently, if you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Best regards,

Kris

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Kris - I createrd a Flow idea per your instructions. This seems like a faulty design to hard code an approval request to show as coming from the person who created the flow. Approvers (managers or otherwise) do not need to know, nor would they care, who created the Approval Flow. This could often be an IT resource. Approvers would primarily be concerned with who created the item requiring approval.

 

I can think of a use case where this hard coding of the Flow creator makes sense for an approval. 

 

Nigel1
Advocate I
Advocate I

The Approval flow email needs to have an option to show who the Approval Request has orginated from rather than showing the default name of who created the flow.

Hello,

The approval email comes from a microsoft.com address you cannot change that.

 

What you can do is insert your people value into the Requestor field in the approval like this, click show advanced options

 

Annotation 2019-10-03 150159.png

The problem isn't the ability to add a "Requestor" merge field into the body of the approval email, it's that the Flow Owner is featured prominently in the first line of the approval request email and is prefaced by "Requested by". In fact, the physical person requesting approval for an item is listed below that. 

 

Therefore, the problem is two-fold in my observation:

  1. The inappropriate hard coding of the phrase "Requested by" to identify the Flow Owner but is not requesting approval for anything. 
  2. The order of the email and inability to edit/move/hide the hard coded pieces. The request originator should be featured more prominently because they are the one actually requesting approval of a thing. They are the one who created the new list/library item, not the flow creator. Most times the flow creator is an IT staff member or the "tech person" on a team, who couldn't care less about the daily approvals occuring on the list itself. 

 

approval.png

 

I agree, this is not very well thought out. I am the IT person at or company, and also the only one with time and knowledge to create these flows. No-one cares that I created the flow. 

 

Example, I am using an approval list for vacation requests. The user puts in their information (dates, times, etc), managers name, and it kicks off the email to be approved or rejected. 

 

The manager receives an email, which shows all that information, but prominently at the top, the mail shows my picture, and "Requested by MY NAME", followed by my email address. 

 

That line is there because I created a flow for others to use, but I keep getting calls asking why I am requesting vacation from them (they are not my manager). It is confusing to the workflow process, and completely unnecessary to show any information about me in this instance, or most others I can think of.

 

The company wants to use sharepoint Online,  as we have been using with an inhouse version for years, but it seems the technology has moved backwards, and is not ready for prime time use yet. I cant do many things that I was able to do with SharePoint designer easily before.

 

If anyone hears or finds a fix for this, Please, let us know!

Anonymous
Not applicable

Also facing the same problem.

 

If the "Requested By: FLOW_OWNER" text simply didn't exist this wouldn't be an issue. If someone requests holiday time by updating a Sharepoint list then whoever gets the approval email does not care about who created the flow. The only info they need is the name of the person who created the list item.

 

This is a major flaw and surely a simple fix.

There is already a field you can change who the requestor is in advanced settings.

Anonymous
Not applicable

How can you change who appears as the requestor? I don't see any field for it in Flow. Where are the advanced settings you're talking about?

Anonymous
Not applicable

This is what I see in flowThis is what I see in flow

 

I see no option for advanced settings.

Hi,

 

It is here and also in start and wait for an approval.

 

it looks like maybe you are using old/deprecated action.

 

Annotation 2019-11-12 215327.png

Anonymous
Not applicable

Thanks for your help and the fast reponse.

OK, better, I did find the newer version that allows the requestor field.. Problem is, Microsoft should not be automatically fielding any of that information. the new version shows requested by: (requestor), and created by: (Myself) now, neither of which do I want to show. I can and do include that information in the body or subject line for the flow in a friendlier more readable format for any flow, if that information is needed, using Dynamic Content. 

 

I get that information is used in the flow itself to make it work, there is just absolutely no reason that information should be provided automatically, especially in this case where there are other means to show that information if wanted. If it must be there, at least it should be in small lettering at the bottom of the email, where my users will not read it, or misconstrue its meaning. My name has no need to be on any communication, post, or end result that user initiated in a flow, unless I am the one initiating that flow for its intended purpose. 

Anonymous
Not applicable

Hello, I stumbled upon this thread as I was sending same request for help. I thought it had to do with SharePoint Permission. I have spend weeks and Months learning Power automate and I need to demonstrate my effort to my department, only to realize that in our testing before the demonstration, my e-mail address is showing in the Requested By and not the actual actual item creators? This is not the kind of development that will be acceptable in my organization. For the time being is there no way i can eliminate my e-mail address from the creator? Yes i created the flow but nobody needs to see that every time, its defeats the purpose and I agree with everyone against this flaw Thank you

I do have the same issue, is the issue fixed? can someone please help me on this

jrauca
Regular Visitor

Still no response from microsoft. Is there any reason why the creator of the flow needs to be tagged?

any update on this? Seems still there's no fix for this.

I don't understand why, when you have no entry in the "advanced" Requester field, there's only the PA creator listed in the email. But as soon as you fill out the advanced field with an email address of the "list created by:" we suddenly need to add a new section, with different, complete unreasonable/confusing information that must be the creator of the workflow (and don't allow it to be removed.) Come on, man! Really?!?!

PS Even this post/topic was hard to find and it only half works. (*shaking-head-in-dismay*) 

THIS SHOULD BE LISTING IN THE KNOWN LIMITATIONS AT A MINIMUM!

I have the same issue and I cannot find an advanced settings for the approval ive got. therefore I have not way to remove the requestor email (the flow creator)!

draxler669_0-1623821940808.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 | Winners will be 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