Dec 16 2022 11:09 AM
Dec 16 2022 11:09 AM
I have a recent issue with a list in SharePoint with multiple People column types.
When I submit an item, the selected users appear fine in the list view. However, when I attempt to edit, those users are empty.
It also doesn't happen with all users. PM and PC work fine, but SD is always removed no matter which People field they are entered in.
I haven't been able to find a correlation between which users work and which don't, and haven't been able to resolve the issue. Any assistance would be appreciated.
Dec 19 2022 07:54 AM
Dec 19 2022 08:18 AM
SharePoint 2019 server patched with KB5002310 and KB5002311.
Display form value of people field (classic mode):
Edit form value of people field: SP takes just another user! Another case is an empty user!!
Dec 22 2022 04:47 AM
@Stefan Goßner Hello, when can we expect this to be fixed? We have various integrated processes within our company that are affected by this. Each item in our lists need to be edited daily to trigger certain workflow email alerts through PowerAutomate, but whenever someone goes to edit an item in a list and saves it, all of the assignee information disappears. This causes us to not only lose that information in that SharePoint item, but also does not trigger our PowerAutomate workflows since the Assignee information is missing. So people are no longer alerted when one of their tasks has been updated.
This has caused a large disruption to our daily work here, especially since we just migrated our information & processes to SharePoint 4 weeks ago. Please let us know ASAP when this will be fixed, or if there is a temporary solution we can implement.
Dec 22 2022 06:53 AM
Dec 22 2022 07:31 AM - edited Dec 22 2022 06:44 PM
So I guess good news is that the data is correct in the list, and only corrupts when you attempt to Edit, so our integrations and workflows are at least working properly in that regard. Our "workaround" has been to save the original values of the People pickers in a text field via workflows so that the data is at least available for later triage if necessary.
Dec 22 2022 07:49 AM
Some feedback on how we deal with the current situation towards the business:Tuesday (after escalation to and investigation together with MS on Monday) we decided to make all site collections readonly, which contains person fields (Powershell script scanning all our 8000 sites).
We assessed the most critical applications to make the site collection accessible again. Many will remain read-only for the coming period till we have a fix.
We have created a MS Forms where site admins can request to make their site active again, but on their responsibility.
We took into account that the fix would take at least 2 or more weeks.I know that MS is busy with the fix, but it takes time.
Dec 22 2022 07:52 AM
Dec 22 2022 04:58 PM
Dec 22 2022 10:32 PM