You’re offline. This is a read only version of the page.
211
Hey everyone,
checked already all other request for this topic but no suggested solution works for me.
I'm working on a flow which is triggered by a Forms answer.
The idea is to get the information out of forms into a SharePoint List as an item. Within that there is a People Picker field which needs to be filled.
While testing Create Item action I got the error message, that this user wasn't found (the user I'm testing with is my own one):
Share
ReportDer angegebene Benutzer wurde nicht gefunden.
clientRequestId: 9e124a4b-23a3-4dcb-8568-4ea1acdd9811
serviceRequestId: 9e124a4b-23a3-4dcb-8568-4ea1acdd9811
| Already checked | Outcome |
| trying if People Picker field is corrupted by manually create an item | Everything works fine as expected |
| using 'responders email' provided by Forms | Error message as above |
| using Resolve User action and using the 'claims' output instead of any email | Error message as above |
| Create Item action suggests users, used one of them instead of an email or 'claim' | Error message as above |
| using Get Profiles to get user information an using these | Error message as above |
| build the 'claim' by myself using [i:0#.f|membership|<email>] via concat() (<email> is replaced with 'responders email' provided by Forms an 'mail' provided by Get Profiles) | Error message as above |
| deleted and reinstalled SharePoint connection | Error message as above |
| added an extra connection for SharePoint | Error message as above |
Right now I'm more than overwhelmed and have no idea where my mistake could be.
Especially that some of the mentioned solutions i tried worked for others.
Thanks for your time.
Hey @bimbam ,
took a bit longer than expected but somehow the PeoplePicker field is now filled through the flow.
It doesn't make any difference if I'm using mail adress or display name.
Maybe it will work for you now as well?
hey @bimbam ,
to be honest I killed my initial idea, cause I wasn't able to find any solution for that, recreated my usecase and found another solution.
Within the next weeks I will try again with another SharePoint List usecase and hope that it just was an issue within that sepcific flow.
All responses (
Answers (
