Forum Discussion
SharePoint Online SP.FieldUserValue.get_email() always returns NULL.
Since last week, SP.FieldUserValue.get_email() has been returning null for all users in Person or Group fields.
This occures when I use getItems method. For example:
var listName = "MyList";
var context = SP.ClientContext.get_current();
var web = context.get_web();
var list = web.get_lists().getByTitle(listName);
var query= new SP.CamlQuery();
var items = list.getItems(query);
context.load(items);
context.executeQueryAsync(()=>{
var enumerator = items.getEnumerator();
while (enumerator.moveNext()) {
var item = enumerator.get_current();
var fldValues = item.get_fieldValues();
console.log(fldValues["Editor"].get_email())
}
});I haven’t been able to find any information about changes related to this behavior. We’ve been using the Email property of user fields for years without any issues, and it has always worked as expected. It's documented here:
https://learn.microsoft.com/ru-ru/dotnet/api/microsoft.sharepoint.client.fielduservalue.email?view=sharepoint-csom
Does anyone know what might have changed or why this has stopped working?
3 Replies
- purna429Copper Contributor
We experienced this issue in PnP PowerShell as well when retrieving the Person or Group filed in a specific scenario like this ( since it may be using CSOM in the backend )
Working :
$item=Get-PnPListItem -List $list -Id 1
$item["Owner"].Email
Not working :
$listItems=Get-PnPListItem -List $list.Title
$item=$listItems[1]
$item["Owner"].Email
We opened a case with Microsoft, and they have confirmed that a fix is being deployed. Here is the most recent update from Microsoft:
#SP1196502
Dec 19, 2025, 1:23 PM EST
We've started deploying the code fix, which has currently saturated 63 percent of the impacted environments. We expect users will experience remediation incrementally while the deployment progresses.
- Lopa_DasCopper Contributor
I see a Microsoft advisory out for this issue now, hopefully resolved soon. Issue ID SP1196502
- Lopa_DasCopper Contributor
We are seeing the same issue, since Saturday. Did you open a Microsoft ticket? Have you heard back anything?