Microsoft Graph mangles SharePoint list number column values












1















I have a SharePoint Online list containing a number column with the following values:




  • 90038946

  • 90000624

  • 90000627

  • 235712345


When I use the Microsoft Graph API the values coming back are mangled:




  • 90038940

  • 90000620

  • 90000620

  • 235712352


This happens both using the MS Graph dotnet sdk as well as the Graph Explorer so it seems to be a feature of the MS Graph API Service.



The REST URI I'm using in Graph Explorer (where OrgUnitCode is the number column) is:



https://graph.microsoft.com/v1.0/sites/<SharePointTenant>,<SiteCollectionId>,<SiteId>/lists/<ListId>/items?$expand=fields($select%3DTitle,Code,Region,OrgUnitCode)


RESULT:



"fields": {
"@odata.etag": ""<GUID REMOVED>,1"",
"Title": "<REMOVED>",
"Code": "<REMOVED>",
"Region": "<REMOVED>",
"OrgUnitCode@odata.type": "#Single",
"OrgUnitCode": 90038940
}


The SharePoint REST API returns the values without mangling the values:



https://<SharePointTenant>/sites/<SiteCollectionName>/_api/web/lists/GetByTitle('<ListName>')/items


RESULT:



...<d:OrgUnitCode m:type="Edm.Double">90038946</d:OrgUnitCode>... 


How do I turn off the mangling feature in Microsoft Graph so I can retrieve the actual values?










share|improve this question





























    1















    I have a SharePoint Online list containing a number column with the following values:




    • 90038946

    • 90000624

    • 90000627

    • 235712345


    When I use the Microsoft Graph API the values coming back are mangled:




    • 90038940

    • 90000620

    • 90000620

    • 235712352


    This happens both using the MS Graph dotnet sdk as well as the Graph Explorer so it seems to be a feature of the MS Graph API Service.



    The REST URI I'm using in Graph Explorer (where OrgUnitCode is the number column) is:



    https://graph.microsoft.com/v1.0/sites/<SharePointTenant>,<SiteCollectionId>,<SiteId>/lists/<ListId>/items?$expand=fields($select%3DTitle,Code,Region,OrgUnitCode)


    RESULT:



    "fields": {
    "@odata.etag": ""<GUID REMOVED>,1"",
    "Title": "<REMOVED>",
    "Code": "<REMOVED>",
    "Region": "<REMOVED>",
    "OrgUnitCode@odata.type": "#Single",
    "OrgUnitCode": 90038940
    }


    The SharePoint REST API returns the values without mangling the values:



    https://<SharePointTenant>/sites/<SiteCollectionName>/_api/web/lists/GetByTitle('<ListName>')/items


    RESULT:



    ...<d:OrgUnitCode m:type="Edm.Double">90038946</d:OrgUnitCode>... 


    How do I turn off the mangling feature in Microsoft Graph so I can retrieve the actual values?










    share|improve this question



























      1












      1








      1


      1






      I have a SharePoint Online list containing a number column with the following values:




      • 90038946

      • 90000624

      • 90000627

      • 235712345


      When I use the Microsoft Graph API the values coming back are mangled:




      • 90038940

      • 90000620

      • 90000620

      • 235712352


      This happens both using the MS Graph dotnet sdk as well as the Graph Explorer so it seems to be a feature of the MS Graph API Service.



      The REST URI I'm using in Graph Explorer (where OrgUnitCode is the number column) is:



      https://graph.microsoft.com/v1.0/sites/<SharePointTenant>,<SiteCollectionId>,<SiteId>/lists/<ListId>/items?$expand=fields($select%3DTitle,Code,Region,OrgUnitCode)


      RESULT:



      "fields": {
      "@odata.etag": ""<GUID REMOVED>,1"",
      "Title": "<REMOVED>",
      "Code": "<REMOVED>",
      "Region": "<REMOVED>",
      "OrgUnitCode@odata.type": "#Single",
      "OrgUnitCode": 90038940
      }


      The SharePoint REST API returns the values without mangling the values:



      https://<SharePointTenant>/sites/<SiteCollectionName>/_api/web/lists/GetByTitle('<ListName>')/items


      RESULT:



      ...<d:OrgUnitCode m:type="Edm.Double">90038946</d:OrgUnitCode>... 


      How do I turn off the mangling feature in Microsoft Graph so I can retrieve the actual values?










      share|improve this question
















      I have a SharePoint Online list containing a number column with the following values:




      • 90038946

      • 90000624

      • 90000627

      • 235712345


      When I use the Microsoft Graph API the values coming back are mangled:




      • 90038940

      • 90000620

      • 90000620

      • 235712352


      This happens both using the MS Graph dotnet sdk as well as the Graph Explorer so it seems to be a feature of the MS Graph API Service.



      The REST URI I'm using in Graph Explorer (where OrgUnitCode is the number column) is:



      https://graph.microsoft.com/v1.0/sites/<SharePointTenant>,<SiteCollectionId>,<SiteId>/lists/<ListId>/items?$expand=fields($select%3DTitle,Code,Region,OrgUnitCode)


      RESULT:



      "fields": {
      "@odata.etag": ""<GUID REMOVED>,1"",
      "Title": "<REMOVED>",
      "Code": "<REMOVED>",
      "Region": "<REMOVED>",
      "OrgUnitCode@odata.type": "#Single",
      "OrgUnitCode": 90038940
      }


      The SharePoint REST API returns the values without mangling the values:



      https://<SharePointTenant>/sites/<SiteCollectionName>/_api/web/lists/GetByTitle('<ListName>')/items


      RESULT:



      ...<d:OrgUnitCode m:type="Edm.Double">90038946</d:OrgUnitCode>... 


      How do I turn off the mangling feature in Microsoft Graph so I can retrieve the actual values?







      sharepoint microsoft-graph






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 27 '18 at 14:34







      Martin

















      asked Nov 22 '18 at 10:34









      MartinMartin

      63




      63
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Microsoft has confirmed that this is a service bug for the SharePoint Graph API.



          https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/321#issuecomment-446754950




          This is a confirmed service bug and has been escalated to the proper team.







          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428974%2fmicrosoft-graph-mangles-sharepoint-list-number-column-values%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Microsoft has confirmed that this is a service bug for the SharePoint Graph API.



            https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/321#issuecomment-446754950




            This is a confirmed service bug and has been escalated to the proper team.







            share|improve this answer




























              0














              Microsoft has confirmed that this is a service bug for the SharePoint Graph API.



              https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/321#issuecomment-446754950




              This is a confirmed service bug and has been escalated to the proper team.







              share|improve this answer


























                0












                0








                0







                Microsoft has confirmed that this is a service bug for the SharePoint Graph API.



                https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/321#issuecomment-446754950




                This is a confirmed service bug and has been escalated to the proper team.







                share|improve this answer













                Microsoft has confirmed that this is a service bug for the SharePoint Graph API.



                https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/321#issuecomment-446754950




                This is a confirmed service bug and has been escalated to the proper team.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 14 '18 at 17:19









                MartinMartin

                63




                63






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428974%2fmicrosoft-graph-mangles-sharepoint-list-number-column-values%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    Refactoring coordinates for Minecraft Pi buildings written in Python