Odata NextLink no work with Api Graph reports

Question

Odata NextLink no work with Api Graph reports

Steph 0

Hi,

When I use the Graph APIs which return JSON, like those for users, no problem, the pagination works well.

But with the Graph report APIs, which are in CSV format in V1.0, when we force beta with the json format, the impression is that it does not understand the following url well

beta/reports/getSharePointSiteUsageDetail(period='D180')?$format=application/json&$top=1000

I only have the 1000 results in the parquet file
wihtout &$top=1000 , only 200.

I tried adding a $ in front $['@odata.nextLink'], same result

1_Config

2-config

In postman, I also have the impression that the whole url is not underlined like in another API but it works when I take it entirely

3-postman

An idea ?

Thanks for your help.

Best regards

AnnuKumari-MSFT 34,566 Reputation points Microsoft Employee Moderator

2023-10-26T10:12:21.14+00:00

Hi Steph ,

Just following up to see if the below answer helped. Please do consider clicking Accept Answer as accepted answers help community as well. Also, please click on Yes for the survey 'Was the answer helpful'

1 answer

Your answer

AnnuKumari-MSFT 34,566 Reputation points Microsoft Employee Moderator

2023-10-26T10:12:21.14+00:00

Hi Steph ,

Just following up to see if the below answer helped. Please do consider clicking Accept Answer as accepted answers help community as well. Also, please click on Yes for the survey 'Was the answer helpful'

Answer 1

AnnuKumari-MSFT 34,566 Microsoft Employee Moderator

Hi Steph ,

Welcome to Microsoft Q&A platform and thanks for posting your question here. It seems like you are facing an issue with pagination when using the Microsoft Graph API to retrieve SharePoint site usage details in JSON format.

Pagination with Microsoft Graph API typically involves using the @odata.nextLink property in the response to retrieve the next set of results.

Could you please try using None : $['@odata.nextLink'] as pagination treats $ as the json starting position. If we do not provide $ then we need to use body else use none property.

Also, please try having the full baseurl instead of separating it with the endpoint as seen in your screenshot.

User's image

Additional resource: Azure Data Factory (ADF) Quick Tip: Using Graph API to Extract Azure AD Information

Paging Microsoft Graph data in your app

Hope it helps. Kindly let us know how it goes. Thankyou.

Steph 0 Reputation points

2023-10-11T09:40:09.2833333+00:00

Hi AnnuKumari-MSFT,

It's ok, thanks you.

just one url

could you tell me the difference between

and

Thanks, have a good day
AnnuKumari-MSFT 34,566 Reputation points Microsoft Employee Moderator

2023-10-23T06:48:58.5266667+00:00

Steph ,

Both of the approach would result in same output.

For pagination rules, we need to create name-value pair where name holds the property name . If the property name is already present in the drop down (ex: AbsoluteUrl) , you can directly select that from the drop down . Or else , you can select None and manually write the property name there.

Hope it helps. Kindly accept the answer by clicking on Accept answer button . Thankyou.
AnnuKumari-MSFT 34,566 Reputation points Microsoft Employee Moderator

2023-10-31T05:18:14.52+00:00

Hi Steph ,

We haven't heard anything from your side on the updates regarding issue resolution. Kindly accept the above answer in case it was helpful. Thankyou.

Share via

Odata NextLink no work with Api Graph reports

1 answer

Your answer