Answered

Flow pulling null email value from the "Created By field"

(0) Share

Report

Posted on by KMac1980

This seems to be extremely rare, but we have one account that Flow is pulling a null value from "Created By" field for the persons email. When you select them in a people picker field it also shows null. We have checked the accoutn in AD and he in facct has a valid email. When you are typing his name in the people picker field in powerapps, his email shows below his name like everyone else's.

We can not find any reason why it is just happening to him. Has anyone had this happen before? I am planning on putting in a ticket with Microsoft, but i wan't to see if anyone else has experienced this at all before I do.

Todd email screenshot.png

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

I have found that you are better off using the ModifiedBy field even when using a created trigger. As you ahve seen the Created by entry isn't always populated fully when the trigger fires. I'm not sure why that happens but when an item is created the person who created it is the last person to modify it also and that entry seems to be reliable.

Was this reply helpful? Yes No
v-alzhan-msft on at

Like (0)

Report

Hi @KMac1980 ,

Could you please share a screenshot of the configuration of your flow?
Which connector that you use that have the empty value in the "Created by email" column?
Please share more details and we could reproduce the issue and fix the issue.

Best regards,
Alice

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

Was this reply helpful? Yes No
KMac1980 78 on at

Like (0)

Report

The flow runs when an item is created in a list. @Pstork1 that is great in theory, but it is not just happening on the created field it's on any people field his account has been put in. In this case, this would not solve the issue.

Was this reply helpful? Yes No
Verified answer

KMac1980 78 on at

Like (0)

Report

Great news! We seem to have found the issue! The users SIP was different from their Office 365 login and their primary email. I am not sure why, but after we made the change, the issue is no longer present!

Was this reply helpful? Yes No
jvdlinden 329 on at

Like (0)

Report

I have found that this could also happen when there is no Exchange plan enabled for the user account that had created the item. That also causes the Email property to be null.
In my scenario, the user was assigned a Office 365 E3 license, but Exchange Online (Plan 2) within it, was not enabled.

Was this reply helpful? Yes No