Problem with New-MgSiteListItem's -Fields property (JSON body is being serialized into camelCase)

Jeremy Bradshaw 31

Hello, this question stems from this open issue - https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/1185. Essentially, when we do:

$fields = @{
    Color = 'Blue'
    Size   = 'Large'
}
New-MgSiteListItem -SiteId "{the site ID}" -ListId "{the list ID}" -Fields $fields

We get: "message": "Field 'color' is not recognized". The 'color' (actually 'Color') field is the alphabetically first field. If we had also included another field that started with 'A' or 'B' for the first letter, the error message would have mentioned that field, and would show its first letter in lowercase.

We can work around this problem by using Invoke-MgGraphRequest or MSGraphPSEssentials' New-MSGraphRequest, so the issue seems to be isolated to the New-MgSiteListItem cmdlet.

I guess the question is just - can you please fix this:)?

Vicky Kumar (Mindtree Consulting PVT LTD) 1,156 Reputation points Microsoft Employee

2022-05-26T06:32:20.32+00:00

Thanks for reporting the issue, is this behavior only exist for New-MgSiteListItem cmdlet ?

Jeremy Bradshaw 31

Hi, I just confirmed the same issue is present with Update-MgSiteListItem. Here's a copy/paste:

> Update-MgSiteListItem -ListId '29d33092-75ef-45da-9935-5feb31786149' -SiteId '0611e8b9-a1a0-4aa5-a81c-e6bb4bb80a12' -ListItemId 1 -Fields @{Color='Red'}

Update-MgSiteListItem : Field 'color' is not recognized
At line:1 char:1
+ Update-MgSiteListItem -ListId '29d33092-75ef-45da-9935-5feb31786149'  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: ({ SiteId = 0611...raphListItem1 }:<>f__AnonymousType104`4) [Update-MgSiteListItem_UpdateExpanded1], RestException`1
    + FullyQualifiedErrorId : invalidRequest,Microsoft.Graph.PowerShell.Cmdlets.UpdateMgSiteListItem_UpdateExpanded1

So, the exact same issue and error.

If we use MSGraphPSEssentials' New-MSGraphRequest or Microsoft.Graph.Authentication's Invoke-MgGraphRequest the problem doesn't occur. Seems to be a problem just with these ***-MgSiteListItem cmdlets.

1 answer

Tong Zhang_MSFT 9,116 Reputation points

2022-05-26T08:07:25.257+00:00

Hi @Anonymous ,

Thanks for letting us know your user experience. When I received the case, I searched a lot of documents did a lot of researches. And I feel regretful to inform you that it is most probably a bug.

We suggest you open a user voice in the following forum. With issue like this increase, the problem may well be fixed in the future. Thanks for your understanding.

Forum:
https://techcommunity.microsoft.com/t5/microsoft-365-developer-platform/idb-p/Microsoft365DeveloperPlatform/label-name/Microsoft%20Graph

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Jeremy Bradshaw 31 Reputation points

2022-05-26T19:30:52.247+00:00

@Tong Zhang_MSFT thanks for the suggestion. I'm not sure if I should accept your response as the Answer. Please let me know. Where it's a bug and not a feature request, I'm hoping that it can get some priority over all the other 'ideas' on the new user voice. We do have workarounds, but that's not ideal because people will have to loop back and update their code/scripts once the proper Cmdlets are fixed. The value of the official modules could become questionable if every issue like this has to be worked around by using Microsoft.Graph.Authentication's Invoke-MgGraphRequest. But I do understand there are likely a boatload of bugs to fix. Just seemed a little surprised about the new UserVoice plan.

Tong Zhang_MSFT 9,116 Reputation points

2022-05-27T02:03:44.497+00:00

Hi @Anonymous .

Thanks for your understanding and support. If you want to raise the priority of this issue, we suggest you go to the website (https://support.microsoft.com/en-sg/help/4051701/global-customer-service-phone-numbers) to find related number and call it to create a new Phone Service Request to Microsoft Phone Support team.

Jeremy Bradshaw 31 Reputation points

2022-05-27T11:29:34.267+00:00

Hi again. Just FYI that MS Support (Premier) has already been attempted and the case was quickly shut down because MS Graph PowerShell SDK is open source and not supported by MS Support, including Premier.

I only mention this here so that anyone else coming along with the same hopes doesn't bother opening a support case.

I'm going to just leave this alone now as I've raised the issue in a few places and have been redirected to different places, 4 actual times (GitHub issue to here; MS Support case to GitHub; Here to the new User Voice, and now here to MS Support). It seems as though GitHub is the sole place where the issue needs to be raised. Then I think the UserVoice can be used in conjunction to boost priority via upvotes.
Sign in to comment