Answered

How to Split Email address and save data in a Person column of SharePoint List

(0) Share

Report

Posted on by hkmamun

106

I have a collection named "SelectedParticipants" which has only 1 column named "Email". Lets say it contains below values:

Email

abc@xyz.com;def@xyz.com;asd@xyz.com;

abc@xyz.com;

abc@xyz.com;def@xyz.com;

I have a SharePoint list Named "PersonList" which have a Person Type column named "Participants" and allow multiple selection

I want to save data to this Participant column base on Email addresses of the "SelectedParticipants" collection

I am using below code

ForAll(SelectedParticipants,Patch(PersonList, Defaults(PersonList),{Title:"test",Participants:If(!(IsEmpty(Email)),ForAll(Split(Email,";"),{DisplayName: Office365Users.UserProfile(Text(Trim(Result))).DisplayName, 
 Claims: "i:0#.f|membership|" & Lower(Office365Users.UserProfile(Text(Trim(Result))).Mail),
 Department: "",
 Email: Office365Users.UserProfile(Text(Trim(Result))).Mail,
 JobTitle: "",
 Picture: ""}))}

but I am getting below error "The requested operation is invalid. Server Response: PersonList failed: The specified user i:0#.f|membership| could not be found."

But if I use any hardcoded value like "abc@xyz.com" in Office365Users.UserProfile() function then data is saving in the Person Type column.

Can you please help what's the wrong I am doing.

Urgent help needed.

Thanks!

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

Community Power Pla... Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

@hkmamun
This error maybe caused by the trailing semicolon in your collection data? When you use Split() I think you are creating a blank Email which Office365Users.UserProfile cannot find, hence the error.

Try removing the trailing ';' from your collection before running your code. You could use a ForAll or AddColumns with Left(columnName, Len(columnName)-1). I haven't tested this but it should work.

The other part you maybe missing is the odata.type ... Shane's Young demos it in this video
at the 18min mark.

Was this reply helpful? Yes No
KrishnaV 5,023 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @hkmamun ,

You need to use the below code block to save the people picker value:
Set(requesterClaim,{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser", Claims:"i:0#.f|membership|" & User().Email, Department:"", DisplayName:User().FullName, Email:User().Email, JobTitle:"", Picture:"" });

If you see any challenge/need further help please let me know I am always happy to do it for my community.

Regards,
Krishna
If this post helps you give a 👍 and if it solved your issue consider Accept it as the solution to help the other members find it more.

Was this reply helpful? Yes No
KrishnaV 5,023 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @hkmamun ,

Change your code block as below:

ForAll(SelectedParticipants,Patch(PersonList, Defaults(PersonList),{Title:"test",Participants:If(!(IsEmpty(Email)),ForAll(Split(Email,";"),{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",DisplayName: Office365Users.UserProfile(Text(Trim(Result))).DisplayName, Claims: "i:0#.f|membership|" & Lower(Office365Users.UserProfile(Text(Trim(Result))).Mail), Department: "", Email: Office365Users.UserProfile(Text(Trim(Result))).Mail, JobTitle: "", Picture: ""}))}

All you missed is:
'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser"

I hope this resolved your issue if you see any challenge/need further help please let me know I am always happy to do it for my community.

Regards,
Krishna
If this post helps you give a 👍 and if it solved your issue consider Accept it as the solution to help the other members find it more.

Was this reply helpful? Yes No
hkmamun 106 on at

Like
a
(1)

Report
Copy link

Link copied!

@KrishnaV thanks for your help, but missing "'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser"" is not a problem. Actual problem is what @Anonymous says.

Was this reply helpful? Yes No