Unanswered

Can't populate variable with parse JSON output

(0) Share

Report

Posted on by DIrk_Meier

Hey community,

I'm running a delta graph query against my AAD users. Idea is to get the users delta each day and store the DeltaLink in a sharepoint file or list - doesn't matter.

As I am getting multiple NextLinks in my flow I want to cycle through them with Do_until so I do get my DeltaLink for running the flow on the next day again.

Can't use pagination in HTTP with delta as this results in a NULL response from the HTTP action. Thats why I want to cycle through the NextLinks

After running the http request I parse the output in JSON. I want to fill a variable with NextLink to start my cycle.

However the value of the variable is NULL when running the flow although the HTTP request and the parse JSON do contain the NextLink Data.

The flow

The variable is of type string, the NextLink Uri is about 10.000 characters so it doesn't run against any limitations.

(The URI can be manually stored in a variable and run without problems)

I have used the HTTP output (body) from this flow as the payload for creating the JSON. So I assume thats not the problem.

Input and Output of analyse JSON do contain the NextLink

The variable will not be filled with data.

The result -> Value = NULL

Whats going on? 😕

Thanks

Dirk

Categories:

Building flows

JSON schema.docx

I have the same question (0)

All responses (2)

Answers (1)

fchopo 8,003 Moderator on at

Like (1)

Report

Hi @DIrk_Meier

You should create different branches in the workflow, depending on whether it's the first call or next ones.

Please, read this excellent post on how to manage those calls: Microsoft Graph Delta Query from Microsoft Flow: Part 3 | AbleBlue LLC

Hope that helps!

Ferran

Was this reply helpful? Yes No
Verified answer

DIrk_Meier 10 on at

Like (0)

Report

Thank you for the feedback, it is something worth considering for the future.
The problem was indeed something else and I was able to fix it.

Parse JSON created items with a wrong terminology.
The second ['body'] is wrong in this case. I had to write the code myself and omit the second ['body'].
Why its doing this I dont't know, the schema is correct and we can't find a reason for the second ['body'] to come up. I was able to replicate this with user and group graph calls using delta in other flows though.

Was this reply helpful? Yes No