I have an auto-created Person lookup field in a record from sharepoint. For new records I want to default the field to the current user. This works fine by setting the default of the lookup to User().
When I access records where this field is set to other users it works correct in the display record form, but then defaults back to the current user when editing the form. This behavior is not correct.
Shouldn't the default only kick in when INITIATING A NEW RECORD? not when editing an existing record?
I noticed similar behavior when creating defaults for data entry items and decided to make two screens, each dedicated to either add or edit. It wasn't much of a hassle since you can easily duplicate screens.
Do you need any further assistance on this?
For editing part, I think @TschoofBAH shared a good idea, creating two editing screen should make it work in your scenario.
Please reply back if you need any further assistance on this.
having separate forms for 'New' and 'Edit' is a good work around for the problem described above.
however, this is still not workign properly. now, the User() appears as a default when i create new records, but when i save records, i get a "field needs a value..." error. only if i manually select the dropdown to resolve the User() email it works. it's like the User() email gets filled into the dropdown, but the actual record doesn't get resolved. not until the dropdown is pressed to "lookup" the record. we look up users from azure AD.
the idea was to have the user field not visible and get filled with the User().
any ideas? thanks and kind regards,
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Did you miss the call? Check out the Power Apps Community Call here.
We are excited to announce the Power Apps Super Users!
Check out our new profile badges recognizing authored solutions!