Hi,
I'm currently in the process of modernizing several SharePoint Designer workflows to MS Flow. One of the flows involves ordering items via a SharePoint list.
Every time a new item is created in a SharePoint list it triggers a Flow. It performs several operations (HTTP request trigger) to set item level permissions (only the approvers and the requester are allowed to see the items). So far so good. But I have run into a small problem with the approvals step.
No matter what I do, the flow always sends out approval emails to the requesters using my name and picture (requested by [my name] + picture) in every mail.
This is troublesome since the creator of the SharePoint item is of course not me but the requester. But the initial mail makes it seem like I was the one requesting the item to be ordered. I have gotten some complaints about this as well.
As far as I could find online this seems to be a bug in MS Flow Approvals? Is this correct? Here are some posts about it that I could find online.
Similar issue
MS Flow idea
Team flow coming from creator
A co-worker said that I maybe could solve this issue by creating the flow directly from the SharePoint list (with the Flow button). Which I did, but this didn't change the end result. The requester is not mentioned in the requested by field. Is there any way I can resolve this or is there anything I did wrong?
Just to summarize:
1.) A new SharePoint item in a SharePoint list is the trigger
2.) This triggers an approval flow (start approvals)
3.) The approval flow isn't sent or appears to be sent from the requester. It appears to have been sent by me (to the approvers).
4.) My own picture is added to the approval mail sent out to management as well.
They want this resolved. At the time of this writing I have done the following:
1.) Built the Flow from scratch starting from the SharePoint list itself (no effect).
2.) Tried to add another connection to the Approval flow step (does not work). The connection that I wanted to add was and admin account.
As a current workaround I have added some more text to the Approval flow (name of the real requester and son on). But this is not an ideal solution.
Is this a bug or can I do something about it in MS Flow so that this issue is resolved? My only other option would be to import this solution into another account (account made for this purpose) and run these flows from there.