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.
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
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.
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
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:
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!
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.
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?
This 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.
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.
I do have the same issue, is the issue fixed? can someone please help me on this
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)!
Episode Seven of Power Platform Connections sees David Warner and Hugo Bernier talk to Dian Taylor, alongside the latest news, product reviews, and community blogs. Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show.
Super Users – 2023 Season 1 We are excited to kick off the Power Users Super User Program for 2023 - Season 1. The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts. Super User Season 1 | Contributions July 1, 2022 – December 31, 2022 Super User Season 2 | Contributions January 1, 2023 – June 30, 2023 Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile. Power Apps Power Automate Power Virtual Agents Power Pages Pstork1* Pstork1* Pstork1* OliverRodrigues BCBuizer Expiscornovus* Expiscornovus* ragavanrajan AhmedSalih grantjenkins renatoromao Mira_Ghaly* Mira_Ghaly* Sundeep_Malik* Sundeep_Malik* SudeepGhatakNZ* SudeepGhatakNZ* StretchFredrik* StretchFredrik* 365-Assist* 365-Assist* cha_cha ekarim2020 timl Hardesh15 iAm_ManCat annajhaveri SebS Rhiassuring LaurensM abm TheRobRush Ankesh_49 WiZey lbendlin Nogueira1306 Kaif_Siddique victorcp RobElliott dpoggemann srduval SBax CFernandes Roverandom schwibach Akser CraigStewart PowerRanger MichaelAnnis subsguts David_MA EricRegnier edgonzales zmansuri GeorgiosG ChrisPiasecki ryule AmDev fchopo phipps0218 tom_riha theapurva takolota Akash17 momlo BCLS776 Shuvam-rpa rampprakash ScottShearer Rusk ChristianAbata cchannon Koen5 a33ik Heartholme AaronKnox okeks Matren David_MA Alex_10 Jeff_Thorpe poweractivate Ramole DianaBirkelbach DavidZoon AJ_Z PriyankaGeethik BrianS StalinPonnusamy HamidBee CNT Anonymous_Hippo Anchov KeithAtherton alaabitar Tolu_Victor KRider sperry1625 IPC_ahaas zuurg rubin_boer cwebb365 Dorrinda G1124 Gabibalaban Manan-Malhotra jcfDaniel WarrenBelz Waegemma drrickryp GuidoPreite If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances. Once they are received the list will be updated.
Join us for an in-depth look into the latest updates across Microsoft Dynamics 365 and Microsoft Power Platform that are helping businesses overcome their biggest challenges today. Find out about new features, capabilities, and best practices for connecting data to deliver exceptional customer experiences, collaborating, and creating using AI-powered capabilities, driving productivity with automation—and building towards future growth with today’s leading technology. Microsoft leaders and experts will guide you through the full 2023 release wave 1 and how these advancements will help you: Expand visibility, reduce time, and enhance creativity in your departments and teams with unified, AI-powered capabilities.Empower your employees to focus on revenue-generating tasks while automating repetitive tasks.Connect people, data, and processes across your organization with modern collaboration tools.Innovate without limits using the latest in low-code development, including new GPT-powered capabilities. Click Here to Register Today!
We are excited to share the ‘Power Platform Communities Front Door’ experience with you! Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well. Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities. Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform. Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.
We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida. Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more. Register today: https://www.powerplatformconf.com/
User | Count |
---|---|
94 | |
36 | |
29 | |
27 | |
23 |
User | Count |
---|---|
122 | |
56 | |
45 | |
42 | |
42 |