You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version
Please specify what version of the library you are using: [3.15]
Expected / Desired Behavior / Question
If there is no user selected in a person field the DynamicForm and PeoplePicker should display the field as empty, regardless of staff members names.
Observed Behavior
We have recently had a new staff member start with the first name 'Null', when editing a SharePoint item built with a DynamicForm or PeoplePicker field if a people field is blank it will default to this staff member 'Null'. This doesn't happen for new items, only when editing an existing one.
Steps to Reproduce
This is happening in web parts and form customizers, in 3.15.
The text was updated successfully, but these errors were encountered:
Fantasticles
changed the title
DynamicForm - Defaults to user with first name 'Null'
DynamicForm & PeoplePicker - Defaults to user with first name 'Null'
Sep 19, 2023
Category
[ ] Enhancement
[X] Bug
[ ] Question
Version
Please specify what version of the library you are using: [3.15]
Expected / Desired Behavior / Question
If there is no user selected in a person field the DynamicForm and PeoplePicker should display the field as empty, regardless of staff members names.
Observed Behavior
We have recently had a new staff member start with the first name 'Null', when editing a SharePoint item built with a DynamicForm or PeoplePicker field if a people field is blank it will default to this staff member 'Null'. This doesn't happen for new items, only when editing an existing one.
Steps to Reproduce
This is happening in web parts and form customizers, in 3.15.
The text was updated successfully, but these errors were encountered: