UserLookupId must now be in string format and no more interger, why?

Pierre-Yves Rosat 1 Reputation point
2023-05-12T11:24:47.31+00:00

Since yesterday, the format for a LookupId field in SharePoint must be in string format and not integer, why?

Body sample before yesterday:

{
    "fields": {
        "TravailEffectue": "Préparation et chargement EP",
        "CollaborateurLookupId": 12,
        "Duree": 120,
        "Date": "2023-05-12",
        "InterventionLookupId": 400
    }
}

and now:

{
    "fields": {
        "TravailEffectue": "Préparation et chargement EP",
        "CollaborateurLookupId": "12",
        "Duree": 120,
        "Date": "2023-05-12",
        "InterventionLookupId": "400"
    }
}

This change in the Graph API crash my mobile app !

Why for an ID Microsoft change the Graph API from Interger to String ?

Microsoft 365 and Office | SharePoint | For business | Windows
Microsoft Security | Microsoft Graph
{count} votes

1 answer

Sort by: Most helpful
  1. Antonio 250 Reputation points Microsoft External Staff
    2023-05-12T12:02:57.29+00:00

    Hi Pierre-Yves Rosat,

    Thanks for posting in the Q&A forum.

    According to the documentation of site resource type for the methods mentioned.

    The default properties of id & sharepointIds are of datatype "string".

    --please don't forget to upvote and Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.