Hi @Maijija117
You are spot on actually nice deduction. In this instance I cannot remember though if its a Header that came back or in the Body.
But if its in the Body, then yes
Do this
1. Run the process one time where you call SharePoint the first time, after that we dont care if it fails
2. Go to the Details page, go to the history of runs, and open the one you just did
3. Copy the Output from the call
4. Add a Parse JSON action
for the Schema click the button as a sample, paste in what you copied
5. For the input, use the Output (might be called body) from the HTTP Request, from the Dynamic Content Window
As long as we copy and paste the right schema and or make sure we pick the right output and level of json path, you will be able to get the odata.nextlink
If you share the flow details with the run I can help more, but you are 150% on the correct path.
P.S. technically you dont need a Parse JSON its just a teaching/learning opportunity. You could use a Compose, click on the Dynamic Content, which will add something like body(...) or output(...) and when you hover over it you will see the total "path" it creates.
If you take that.. and you visually look at the output, you can figure out the path to the odatalink
Imagine the out put looks like this
body('HTTP_REQUEST')['body/value']
And when you look at the Response JSON, you can clearly see the value Object. Thats your start path
And if the odatalink is simply a child then you would have
body('HTTP_REQUEST')['body/value']?['odata.nextlink']
Just an example but another way.
Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey
