Handle the pagingCookie and limitCount on Record Change History

[GoogleCodeExporter]

The RecordChangeHistoryResponse message includes a Paging Cookie element.

However, according to the SDK documentation, this is not implemented in the 
.NET class:
http://msdn.microsoft.com/en-us/library/microsoft.crm.sdk.messages.retrieverecor
dchangehistoryresponse.aspx

This suggests that these fields will never be used, and therefore can be 
discounted when sending the Request.

This needs to be confirmed before the related parameters can be removed from 
three functions:
* generateRetrieveRecordChangeHistoryRequest
* retrieveRecordChangeHistoryRaw
* retrieveRecordChangeHistory

Original issue reported on code.google.com by N.M.Pr...@gmail.com on 15 Mar 2012 at 12:34

[GoogleCodeExporter]

Changed to Review task

Original comment by N.M.Pr...@gmail.com on 15 Mar 2012 at 12:43

• Added labels: Type-Review

[GoogleCodeExporter]

By default, CRM allows 5000 records per message (e.g. in RetrieveMultiple).

We can assume that the RecordChangeHistory will have either no limit, or the 
same limit - so this functionality will not be required unless we have over 
5000 changes in the history of an Entity.

At that point, experimentation will be needed to determine 
* What format is the PagingCookie returned on the Response?
* Where can this data be included in the Request?

Original comment by N.M.Pr...@gmail.com on 16 Mar 2012 at 2:08

• Changed state: Accepted