You need to enable Pagination. What version of IDM is this - you might need to use 4.8.6 or later to get the option (I did not see it with 4.8.5, but 4.8,7 does show it).

And please, do report back on how it works.

Have anyone made this work?

I have a response like this : 

{
"@odata.context": "">connector.mindkey.com/.../$metadata
"@odata.count": 3026,
"value": [
{
.......
}
],
"@odata.nextLink": "">connector.mindkey.com/.../PositionVersion
}

I have set the driver to 

When does the next page "happen"?

I call the endpoint - then i read the data by grabbing xpath(.) and using javascript i extract my data.

Then i work on the data and in this case add my employees and then i do strip xpath (.) 

Otherwise i get something like "error because of opperation data in input element"

Then my driver kinda stops..

So when are the Driver calling the next page? have i stripped the next page information? Can i add it with xpath somehow?

I THINK the shim is expecting your JSON->XML to spit out an <instance> doc and probably with a <query-token> node specifying the next node.  SO in your case, @odata.nextLink in some format. 

I THINK the shim is expecting your JSON->XML to spit out an <instance> doc and probably with a <query-token> node specifying the next node.  SO in your case, @odata.nextLink in some format. 

Hm ok.

Im having some trouble wrapping my head around how the driverconfiguration actually works..

Im on the publisher channel in "poll"-mode so data flows into the IDM i get a response body from the pull wich i work on and thats all fine, but when should the driverconfiguration regarding paging actually do its job? seems to me that it should "work on its own" without me tampering with the xml dokument (other than getting my data out). 

And if i were to create a query in my own code, disregarding the driverconfiguration, how would it travel alle the way around to the subscriber channel and make a new poll/query?

Does anyone have a document with either the driverconfiguration working or a modified document with a query, that I can replicate in my driver?

Geoffrey Carman said:

THINK the shim is expecting your JSON->XML to spit out an <instance> doc and probably with a <query-token> node specifying the next node

Polling functionality is all self-contained within the shim from what I understand.

The JSON->XML translation always happens on the engine side, not in the shim.

What is confusing, is that like the AD driver, the default engine side policies call out to a java class that is normally bundled with driver shim updates. When per best practice, one runs the driver shim on a separate remote loader, it is far too easy to forget to update/patch/install this java class on the engine side, which can cause engine side policy evaluation to fail.

Now don't get me started on how broken and poorly written the built-in JSON->XML implementation that ships with the REST driver is. One of the first things I do when working on a REST driver is to replace this with a less broken and more flexible approach (several options exist).