Save a Selected email from Collection to a Sharepoint list Person column (Not using Patch)

[WorkingRicardo]

I got this code, it collect the emails of all people in my country considering everyone below the country boss: 

ClearCollect(colTeam1;UsuariosdeOffice365.DirectReports("CountryBoss@company.com"));;
//collect managers
ClearCollect(colTeam2;Ungroup(ForAll(Filter(colTeam1;!IsBlank(Mail));UsuariosdeOffice365.DirectReports(UserPrincipalName));"Value"));;
//collect ordinary users
ClearCollect(colTeam3;Ungroup(ForAll(Filter(colTeam2;!IsBlank(Mail));UsuariosdeOffice365.DirectReports(UserPrincipalName));"Value"));;
//collect them all
ClearCollect(colTeam;colTeam1;colTeam2;colTeam3)

The on the DataCard for the Person column I have this on Update: (have tried "Selected.Mail - DisplayName - etc" but gives errors)

DataCardValue19.Selected

For the comboBox in Items I have this: 

Filter(colTeam; !IsBlank(UserPrincipalName))

Witouth that, there would be blank items. 

The error I'm encountering if that my button with "SubmitForm(SharePointForm1)" does not save whatever you select. I need to avoid using Patch, so I need a way to save the selected person. The error it normally shows in PowerApps, is that the Update part expects a Record value. 

[WiZey]

Can you try submitting the form without the person's datacard? Just to be sure the error is related to this field.

[WorkingRicardo]

@WiZey Yep, without the datacard I can both create new entries and edit them no prob.

[WiZey]

And you're saving the selected user in a person-field or a text-field?

[WorkingRicardo]

A person field 😞 @WiZey 

[WiZey]

You're surely feeling how I'm starting to lack ideas and solutions by now, but let's just try keeping a positive attitude and do our best.

A person-field expects a record with this structure. Anything else is not compatible and throws an error.

{
    Claims: "i:0#.f|membership|" & Mail;
    Department: "";
    DisplayName: "";
    Email: "";
    JobTitle: "";
    Picture: ""
}

Your combobox is populated by a list of person from "Office365Users" connector. Its structure is different, however, all we need is the "Mail" part of the selected person. Which brings us back to "Datacard.Selected.Mail".

The "Default" value of your datacard is the result of a "LookUp()" on your collection "colTeam", which correctly gives a person based on the saved value in your SharePoint list. We can see it's correct because the dropdown automatically shows the correct person when editing a record.

That leaves us with the creation of a new record. 

At first, the combobox is certainly populated, and its default value is certainly blank at this point. Selecting a person must not reset the combobox's selected value, and the record in the "Update" property must be valid. You can verify it by checking if "Datacard.Selected.Mail" has a value. If it's blank, it's bad.

My advice is to check and MAKE SURE the "Update" property is valid. "Datacard.Selected.Mail" has to hold a value and "Claims" must be valid too. You can also check in the "Updates" output of the form to see in details if everything is right.

[WorkingRicardo]

@WiZey Hey... It's ok 😞 I imagined that at some point there might not be any possible fixes T_T.... Thanks so much for bearing so long with me.

But yeah, the Update part does have an email in the mail part and other parts of the table for the Selected:

I haven't tried filling the rest of the fields (Display name - department - pictture , etc). Maybe the error is there? I just input "Selected.Display/Picture/etc" depending on the case?

Edit: already tried and failed as well xd Altough for picture i left it with the "" because i didnt know with what Selected it would match

[WiZey]

From my experience, "Claims" is the only mandatory property in the record. Everything else can be left blank and it won't make a difference. 

Sorry, I'm just left clueless as to what could be the issue here. I repeated the same steps as you did, but I can't reproduce the error. 

I can only wish you good luck in your endeavor; try different solutions. And if it's still not working, you can still open a new topic to bring it up and hopefully someone will spot the issue here.