This project has moved and is read-only. For the latest updates, please go here.


Lists.GetListItemChangeSinceToken operation input parameters not defined



Hi Marc,
While looking into how GetListItemChangesSinceToken works, I found that it is not setup to accept CAMLQuery as one of the input parameters.. In looking at the source, looks like (perhaps?) you did not setup the input parameters as you intended (according to the documentation page)
Here is the snippet of code from v2013.01:

case "GetListItemChangesSinceToken":
    addToPayload(opt, ["listName", "viewName", "query", "viewFields", "rowLimit", "queryOptions", "changeToken", "contains"]);
The documentation states the input parameters to be (bold items are those that don't seem to be supported):
  • [webURL]
  • listName
  • viewName
  • CAMLQuery
  • CAMLViewFields
  • CAMLRowLimit
  • CAMLQueryOptions
  • changeToken
  • contains
I'm assuming this operation's input parameters should mirror closely what the GetListItems operation is defined as:
case "GetListItems":
    addToPayload(opt, ["listName", "viewName", ["query", "CAMLQuery"], ["viewFields", "CAMLViewFields"], ["rowLimit", "CAMLRowLimit"], ["queryOptions", "CAMLQueryOptions"]]);
(Plus the input parameters specific only to GetListItemChangeSinceToken).

Closed Dec 28, 2013 at 7:49 PM by sympmarc
Released in 2013.02


sympmarc wrote Oct 4, 2013 at 7:38 PM

Fixed in 2010.02ALPHA2

sympmarc wrote Oct 4, 2013 at 10:02 PM

ptavares wrote Oct 8, 2013 at 4:22 PM

I can confirm that this is resolved. I also validated that it works on SP2007 with the changes you put in to recognize when a xml element t should not be sent to the server... Works like a charm...

Thank you very much...

ptavares wrote Oct 8, 2013 at 4:26 PM

I should have mentioned... I have not re-ran some tests on SP2013 and 2010, but I don't expect an issue there.. If I see one, I'll report back..

sympmarc wrote Oct 8, 2013 at 7:36 PM

Excellent! Thanks for testing...