Cannot Patch person column to sharepoint list.

[RVoller]

Hi,

I have tried to PATCH to a SharePoint List, but have been unsuccessful.  Not sure what else I should be doing.

The data are captured via a combo box.

Items : 

If(!IsBlank(Trim(RecommendCombo.SearchText)), Office365Users.SearchUser({searchTerm: Trim(RecommendCombo.SearchText), top: 5}))

Error I am getting is - Invalid argument type. Expecting a Record value, but of a different schema.

Patch (

    'Asset Disposal/Transfer Requests-DEV',

    Defaults('Asset Disposal/Transfer Requests-DEV'),

   {Title: AssetDescTxt.Text},

    {'Disposal or Transfer?': {Value: (DisposalRadio.Selected.Value)}},

    {Justification: JustificationTxt.Text},

    {Department: DepartmentTxt.Text},

    {'Existing Capex': ExistCapexTxt.Text},

{

    'Recommended by': {

        '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",

        Claims: "i:0#.f|membership|" & User().Mail,

        Department: "",

        DisplayName: User().FullName,

        Email: User().Email,

        JobTitle: "",

        Picture: ""

    }

})

[Amik]

@RVoller - to Patch a SharePoint Person column based on a Combo Box which is linked to Office365Users, the correct syntax would be: 

Patch (
    'Asset Disposal/Transfer Requests-DEV',
    Defaults('Asset Disposal/Transfer Requests-DEV'),
    {
        'Recommended by': {
            DisplayName: RecommendCombo.Selected.DisplayName,
            Claims: "i:0#.f|membership|" & Lower(RecommendCombo.Selected.Mail),
            Department: "",
            Email: Lower(RecommendCombo.Selected.Mail),
            JobTitle: "",
            Picture: ""
        }
    }
)

Could you confirm if the above also fails?

[RVoller]

Hi,

Yes, it does fail.

[RVoller]

I noticed that there is an extra ','  in the query after defining the datasource.  I removed the extra ',' and I got the original error.

[Amik]

@RVoller - I will defer to @WarrenBelz and @timl  - who might notice something obvious.

[RVoller]

Thanks, that would be great.  Just also letting you know that I included the 'odata' connection reference as well and that did not work either.

[WarrenBelz]

@Amik ,

This may be a multi-value person field.

[timl]

Thanks for tagging me @Amik 

@WarrenBelz - This is a good suggestion however, I notice that in an earlier post, the field is a single person. It's a long thread so it is easy to miss this.

@RVoller - At this point, I would suggest that you try to provide the minimum amount of data just to try to achieve a successful patch. The only value you need to specify is your email address - I would hard code your email address in the claims section.

Patch (
    'Asset Disposal/Transfer Requests-DEV',
    Defaults('Asset Disposal/Transfer Requests-DEV'),
    {
        Title: "Record Title",
        'Recommended by': {
           '@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
            Claims: "i:0#.f|membership|rvoller@email.com",
            DisplayName: "",
            Department: "",
            Email: "",
            JobTitle: "",
            Picture: ""
        }
    }
)

Another thing to clarify is how did you create this SharePoint list (e.g., did you create this by importing an Excel spreadsheet?), or have you renamed any of the columns in the SharePoint list?

SharePoint has a notion of internal and external column names. If any point you renamed the 'recommended by' column, the column that you specify in patch may not correspond to the column that you expect.

[mmbr1606]

this is how i always patch person fields with no issues

Let me know if my answer helped solving your issue.

If it did please accept as solution and give it a thumbs up so we can help others in the community.



Greetings

[RVoller · Accepted solution]

Hi Team,

Thank you for all the responses.

We have discovered that this error is specific to the person columns of this list. 

As per @WarrenBelz , there was a possibility that the list may have been changed over time, columns renamed, etc.

After trying several options including changing the permissions of the list and the site, we decided to re-create the list from scratch.

This worked successfully and we are able to Patch the Person column.

Thank you, once again.