Inconsistent Retrieval of siteId, listId, and uniqueId for SharePoint Pages via Graph API

Question

Hi Microsoft Support,

I’m encountering an inconsistency with the Microsoft Graph API when retrieving images from SharePoint posts. Here's the issue in detail:

API Workflow:

1. Initial Request: I use the endpoint: https://graph.microsoft.com/beta/sites/${pageId}/pages to retrieve attributes related to SharePoint Pages.

Expected Response: In most cases, the response includes the siteId, listId, and uniqueId attributes. I use these attributes in the subsequent request: https://graph.microsoft.com/v1.0/sites/${siteId}/lists/${listId}/items/${uniqueId}/driveitem This normally allows me to access the uploaded images from the SharePoint posts.

Issue:

In some cases, when images are uploaded to SharePoint posts from a device, the siteId, listId, and uniqueId attributes are not included in the API response. This happens even though the upload process is identical for both cases.

• Expected Behavior: The attributes siteId, listId, and uniqueId should always be present for images uploaded via the same method.
• Observed Behavior:
  • Case 1: Uploading an image to a SharePoint post includes the expected attributes (siteId, listId, uniqueId).
    • Case 2: Uploading an image in the same manner to another SharePoint post does not include the attributes.

Question:

Why is there inconsistency in retrieving these attributes for images uploaded to SharePoint posts? Is this a known issue or a limitation of the Graph API?

Any guidance or insights into resolving this issue would be greatly appreciated.

Answer 1

Hi @Apps Dev,

Per my test, I could get siteId and uniqueId in parentReference. But there is no listId in my test result. This should be the expected result refer to the offical document:

driveItem resource type

And here is my test result

---

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.

Answer 2

What we do:  We are provided services to multiple clients so that they can manage their sharepoint news posts

The flow:

• The user/client signs in with Auth2.0 into azure with scopes:  'Sites.Read.All User.Read openid profile offline_access'.
• From 'https://graph.microsoft.com/v1.0/sites?search=*&$orderby=lastModifiedDateTime' we get their pages from which they select the page from which the news post they want to manage.
• We then call 'https://graph.microsoft.com/beta/sites/${pageId}/pages?$orderby=createdDateTime desc&top=60' to get a collection of all the latest news Post they have on that page (we filter the results based on "promotionKind": "newsPost" attribute).

The problem: We assumed we can find the image deeply nested inside {titleArea.serverProcessedContent.customMetadata.value} from which we use listId,siteId,uniqueId to call 'https://graph.microsoft.com/v1.0/sites/${siteId}/lists/${listId}/items/${uniqueId}/driveitem' BUT, this is not always the case. Most often than not, this image_item is not available, thus we cannot retrieve their image.

Question: Is there something wrong with the assumption we have? Is there a better api-flow we should follow to retrieve the news posts along with their images?

Notes: It is ok to instruct the client on how to upload the image so that the api-flow can work.