CreateLink for item with provided Id sends improper query to SharePoint resulting in incorrect error.

[fishinstew]

While providing an _itemId to Graph an improper query is executed vs SharePoint and an incorrect error is bubbled up through Graph.

Steps To Reproduce: With an authenticated Microsoft.Graph.GraphServiceClient, perform the following action vs a SharePoint site with > 5,000 items.
await GraphClient.Sites[_siteId].Drives[_driveId].Items[_fileId].CreateLink("view", "anonymous").Request().WithMaxRetry(0).PostAsync();

• You may need to enable anonymous link sharing, as this is not enabled by default
• You also need to ensure that WithMaxRetry is set to 0 to see the error. If this is not added to the request you will simply receive an error code of "tooManyRetries" which is another problem that i'm not going to worry about here.

Observations:

• Graph returns an HTTP Status code of 429 and an error code of "throttledRequest" with a message of "The request has been throttled".

• The premier support rep for SharePoint stated that the query being sent by graph prior to attempting to get link was an improper 'recrusive' query causing a ListViewThreshold error. He stated that it should be sending a more simple/direct query to get the item by the provided id:

`

{b9d187fb-6b52-4e54-9553-e5605b982a3c}

<ViewFields>
    <FieldRef Name='owshiddenversion'/>
    <FieldRef Name='SharingDocId'/>
    <FieldRef Name='CurrentLink'/>
    <FieldRef Name='AvailableLinks'/>
</ViewFields>
<RowLimit Paged="TRUE">2147483647</RowLimit>

`

• As a result of this ListViewThreshold error being returned to Graph, an invalid 429 "throttledRequest" with no retry-after header was bubbling up. This appeared to cause the Graph Client to default to it's 3 second retry causing it to hit the "tooManyRetries" error initially. This resulted in my team to run in circles... chasing the wrong problem and ultimately having to use a Premier Support ticket to figure out what was really wrong.

Expected Behavior:

1. When providing an _itemId and calling "CreateLink" the recursive all query should not be executed vs. the SharePoint instance to locate the item. Instead a more direct query should be made to both improve efficiency and prevent problems with larger SharePoint sites.
2. When a ListView threshold error is thrown by SharePoint, a more correct error should be returned via the GraphApi with the SharePoint exception nested as an Inner Exception to prevent $ and Time being lost. AB#7243

[MIchaelMainer]

@JeremyKelley This appears to be an issue with SharePoint+Graph service when creating an anonymous sharing link.

[petrhollayms]

Thank you for reporting this issue. This appears to be an issue or limitation with the service APIs. Unfortunately, as the Microsoft Graph SDK team, we do not have ownership of the APIs that are causing you issues. We invite you to create a question about the service API to Microsoft Q&A and tagged with one of the [microsoft-graph-*] tags, that way it will get routed to the appropriate team for them to triage:

https://aka.ms/msgraphsupport or directly https://aka.ms/askgraph

For now, we will close the issue on our side but feel free to open it in the relevant repository if you think the issue is specific to SDK. Please let us know if this helps!

Note: We will close this repository on April 19, 2024.