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?

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. 

ChrisKnudsen said:

When does the next page "happen"?

In your case, I believe this happens in the driver shim itself. So you cannot intercept and manipulate it in policy.

Your driver-parameters look to be correct given your example.

Possibly stating the obvious, but applying the driver package is only half of the picture here.

You also need to update the driver shim to a version that knows how to deal with the pagination parameters. (preferably use the absolute latest shim available). For easier testing and debugging suggest you use a dedicated remote loader instance for this shim.

If you can, post a more detailed driver-side trace that includes driver startup and first poll. Set driver trace level to 99.