Skip to main content

I have created a workbench that loops through an odata/json url using nextlink. I then placed a tester to stop running after the url returns no value. My problem is that this starts over after it runs the full data-set and repeats never stopping. A 700 feature table ran over the weekend had 70,000 and still counting.

Is the entire dataset repeated, or is it the last page that repeats endlessly?

Do you clear the nextlink at the end of the loop?

If the @odata:nextLink is not present, it won't overide the existing attribute from the previous iteration.


Is the entire dataset repeated, or is it the last page that repeats endlessly?

Do you clear the nextlink at the end of the loop?

If the @odata:nextLink is not present, it won't overide the existing attribute from the previous iteration.

Thank you for the feedback. Looks like my issue was in the Published parameters. I create list of choices to append to the core url to select specific tables. I then use metadata to define the columns. This parameter needed to be passed to the looper. I found that i have hard coded the url in the looper http caller so when i changed tables on the workbench it was looping what actually was the largest table with millions of rows. My bad 🙂

 

 


Reply