SharePoint Modified By column not returning in Email output

[Anonymous]

Hi,

I need a Flow to email the 'Modified By' entry within a SharePoint document library. This being a default field, it's obviously configured as OOB.

When using this in Flow to try & send an email, it fails, with the 'To' field in the error being blank despite originally being configured with the 'Modified By Email' field:

I then decided to do a bit of further analysis to send myself an email detailing ALL fields for both Created By and Modified By columns:

Oddly, the email output details all info for Created By, but nothing for Modified By:

Is this a known issue/bug? It seems a bit odd that Flow can read one of the default Person fields in the library, but not the other.

Thanks

[WillGlynn]

Hi CragWhite.

was just doing a search for this! as i also have the same issue.

i have a flow that was working up till at least yesterday and it was using the 'Modified by email', to send an email.

The information was coming from the trigger of the flow ' when a fiile is created or modified (properties only).

is this a bug i wonder or have they removed that from use? but why leave it in the aea for dymanic content...

hopefully some one has an answer.

regards

W

[wnzn]

I can confirm this was working but is no longer. Here is another forum post on the topic: https://powerusers.microsoft.com/t5/Building-Flows/Trigger-SharePoint-When-a-file-is-created-modifie...

I am seeing this behaviour in LogicApps as well as Flow and have logged a support ticket for this. I'll keep you updated should this get resolved.

[Anonymous]

Raising a ticket was on my list to do this morning - thanks for beating me to it. I look forward to a resolution, hopefully

[wnzn]

So the promised follow-up: we've been informed the product group is working on a fix which should be rolled out to all regions by the end of next week.

[Anonymous]

Thanks for the update, appreciated.

It's a shame that there's no visibility of this in the O365 Admin Center > Service Health, but at least work is being done.

[WillGlynn]

i'll 2nd that.

Cheers for the update.

W

[v-yuazh-msft · Accepted solution]

Hi @ CraigWhite,

Have your problem be solved?

I have made a test on my side and I don't have the issue that you mentioned.

My flow's configuration as below:

 

The flow run successfully as below:

 

Please try your flow again and feel free to reply here if the problem still exists.

Regards,
Alice Zhang

[Anonymous]

Hi @v-yuazh-msft

I have just re-run the Flow that was erroring last week, and can confirm that details of both Created By and Modified By are now being successfully retrieved.

Thanks

Craig