cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate III
Advocate III

Store email address of last editor for re-use in next workflow

I have a working Flow, triggered when a SP list item is updated. It checks if status field value is = "completed" and if yes, sets the status to "pending tracker update" and sends a notification email to the person who tracks completion of items.

 

Once the tracker is updated (manually, automation of this step is not straightforward for several reasons), the person sets the status to "tracked" and provides a tracking ID.

 

So far so good, but now I want to notify the original submitter (not the "Created by", but the "Modified by" who set the status to "completed", unlikely the same person). I've added a column to the SP list called "Submitter" and wanted to populate it with the "Modified by" email address at the same time I update the status to "pending tracker update".

 

I tried with a person field and with a single line of text field in the SP list, but to no avail. I either only get a field Submitter Claims with no dynamic content available (person) or an error that the email attribute is not possible with data of type string.

 

I tried with the Compose action but couldn't figure it out. Any help is highly appreciated!

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted
Community Support
Community Support

Re: Store email address of last editor for re-use in next workflow

Hi @Beat,

 

Could you please share a screenshot of your issue?

Could you please show a bit more about the value that you provided within the Submitter column?

 

Please check if the email address that you provided within the Submitter field belongs to your Office 365 Organization (group) or SharePoint group. If you provided an email address which is not existed in you Office 365 Organization (group) or SharePoint group, I afraid the flow would fail.

 

In addition, please check if you have filled proper values within other fields of your "Update item" action. Please also take a try to re-create your flow and then check if the issue is solved.

 

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.

View solution in original post

Highlighted
Advocate III
Advocate III

Re: Store email address of last editor for re-use in next workflow

@v-xida-msftHi again, since my flow was exactly what you suggested and should work, I decided to delete it and start from scratch. This did the trick. But I'll never know what was wrong with it in the first place 😞

Thanks anyway, I'll possibly consider again first starting from scratch (rather than scratching my head for hours) in circumstances where a flow behaves odd.

View solution in original post

4 REPLIES 4
Highlighted
Community Support
Community Support

Re: Store email address of last editor for re-use in next workflow

Hi @Beat,

 

Could you please share a screenshot of your flow's configuration?

Could you please show more details about your SharePoint list?

Further, do you want to update the Submitter column with Modified By Email address when the Status field value is equal to "completed"?

 

I have made a test on my side and please take a try with the following workaround:5.JPG

Within the Submitter Claim field, type the Modified By Email dynamic content as a custom value.

 

Note: The Status column is a Choice type column in my SharePoint list, the available values of it are pending tracker update, completed and tracked. The Submitter column is a Person or Group type column in my SharePoint list.

 

The flow works successfully as below:6.JPG

 

7.JPG

 

 

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.
Highlighted
Advocate III
Advocate III

Re: Store email address of last editor for re-use in next workflow

@v-xida-msftHi Kris, that's exactly how I have set it up. The Submitter column is a Person or Group column, but for some reason it can't store the Modified by Email value in there. I'm getting the following error:

 

{
  "status"400,
  "message""A value must be provided for item.\r\nclientRequestId: 65883583-b9c0-473a-accb-6ba71b5b5a68",
  "source""sharepointonlineconnectionprovider-westus.tip0-westus.p.azurewebsites.net"
}

 

If I change the Submitter column to Single Line of Text, this works fine and it populates the field with the correct email address.

 

However, since it is a text field, I can't use it in the subsequent workflow as an email address.

Highlighted
Community Support
Community Support

Re: Store email address of last editor for re-use in next workflow

Hi @Beat,

 

Could you please share a screenshot of your issue?

Could you please show a bit more about the value that you provided within the Submitter column?

 

Please check if the email address that you provided within the Submitter field belongs to your Office 365 Organization (group) or SharePoint group. If you provided an email address which is not existed in you Office 365 Organization (group) or SharePoint group, I afraid the flow would fail.

 

In addition, please check if you have filled proper values within other fields of your "Update item" action. Please also take a try to re-create your flow and then check if the issue is solved.

 

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.

View solution in original post

Highlighted
Advocate III
Advocate III

Re: Store email address of last editor for re-use in next workflow

@v-xida-msftHi again, since my flow was exactly what you suggested and should work, I decided to delete it and start from scratch. This did the trick. But I'll never know what was wrong with it in the first place 😞

Thanks anyway, I'll possibly consider again first starting from scratch (rather than scratching my head for hours) in circumstances where a flow behaves odd.

View solution in original post

Helpful resources

Announcements
FirstImage

Microsoft Ignite 2020

Check out the announcement of Power Platform content at Microsoft Ignite!

thirdImage

Experience what's new for Power Automate

Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (3,868)