Hi I am accessing Sharepoint list items using Http action.
I added the bearer token as Authorization header .
When the flow runs it failed and throw this error :
Can you please share more information on this? (As to what context are you using the generic Send HTTP request or the Send HTTP request to SharePoint to get item(s) considering that one can use the Get Item and Get Item(s) actions directly). Just trying to understand the backgound for these actions before diving into identify the issue.
Is there a particular reason you don't want to use the Send HTTP request to SharePoint instead of the generic HTTP connector? The generic connector is a premium feature while the SharePoint HTTP request is standard. In terms of the HTTP you send they should allow for the same payload. You might have better luck with the one designed to work wiht SharePoint.
My Scenario was the following :
I want to set item level permission using MS Flow like this article steps
When I tried to do that HTTP action to break inheritance after creating the bearer token it throw the mentioned error "Item does not exists"
So I tried to do same with "Send HTTP request to SharePoint" It is working correctly.
I thought it might be my token permission issue so I changed to give it fullControl
then tried but same error .
Finally, I tried to simplify the issue by tring HTTP action to get item not Sharepoint default get item action .
but same issue happen.
The article does not mention under which context flow should run so I followed the same.
All articles are talking about HTTP request :
For that I tried to use the same.
With Sharepoint actions everything is working perfectelly .
It should work also with HTTP action as article mentioned but for some reason it throw this error so I want to know why this happens?
There can be more than one reasons for this issue that you are facing. And those could include Caching, delays, browser support, mapping the correct IDs, lists and the site etc. Addressing these issues, the send HTTP request to SharePoint was brought in and that has replaced all the heavy lifting and the tedious process of the authorisation token and doing it the traditional way.
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Those articles pre-date MS releasing the SharePoint HTTP call. The new action was released when the original HTTP request action was made a premium feature in Feb, 2019. Since there are things that only work via HTTP in SharePoint MS released a special version that works with SharePoint that is standard. I agree it should work with the regular HTTP request, but the SharePoint one should be easier (and cheaper) to use.
I don't think it is related to any of factors you mentioned because in browser I can do same action and get results .
It is related to HTTP action with bearer token to get List Items .
When I used same HTTP action with access token to get user claim it worked and retrieve user data
Why this happens only on list item level ?
Maybe/ maybe not. Can you please try doing this: In the URI, remove everything after the items '(id)' and run te flow and check what data is being returned?
Hi @Emad_Gerges ,
Since the error message shows that Item does not exist, please try to output ID, and then check whether the item corresponding to the item ID exists in the List.
Or you could choose the Basic authentication method and enter valid username and password to test.
Besides, I think Get item action and Send an HTTP request to SharePoint included in SharePoint connector are still the first choice. Use them to easily meet your needs.
The item exists in the list and can be accessed by normal HTTP to SharePoint action but cannot be accessed by normal HTTP action with bearer token