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

Lists.GetListItemChangeSinceToken operation input parameters not defined

Sep 21, 2013 at 10:27 PM
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).

Oct 4, 2013 at 7:33 PM
Right you are. I don't think I've ever used that operation. Good catch!

Oct 4, 2013 at 7:33 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Oct 4, 2013 at 9:06 PM
Thanks Marc..

Question: My current work-around is to set both parameters (ex. set both query and CAMLQuery)... will that cause an issue once you provide the fix?

Oct 4, 2013 at 9:24 PM
I think it will. What I'm doing in the ["query", "CAMLQuery"] syntax is handling the instances where I used non-standard element names early on. You should use one or the other.

I'll post an alpha shortly with the fix so that you can try it: 2013.02ALPHA2.

Oct 4, 2013 at 10:05 PM
Just posted. I also have the fix in place for the "contains" and "changeToken" columns. Give it a go and let me know how it works for you.

Oct 4, 2013 at 10:10 PM
That was quick... :)

Thanks Marc... Will try and let you know...