I\'m querying MS Dynamics CRM Online from my console app:
public EntityCollection GetEntities(string entityName)
{
IOrganizationService proxy = ServerCon
You can only get back 5000 records at a time using fetch XML.
To get more records, you have to use a paging cookie, see here:
Sample: Use FetchXML with a paging cookie
The relevant bits of code:
// Define the fetch attributes.
// Set the number of records per page to retrieve.
int fetchCount = 3;
// Initialize the page number.
int pageNumber = 1;
// Specify the current paging cookie. For retrieving the first page,
// pagingCookie should be null.
string pagingCookie = null;
The main loop modified, since the sample doesn't seem to do update the paging cookie:
while (true)
{
// Build fetchXml string with the placeholders.
string xml = CreateXml(fetchXml, pagingCookie, pageNumber, fetchCount);
FetchExpression expression = new FetchExpression(xml);
var results = proxy.RetrieveMultiple(expression);
// * Build up results here *
// Check for morerecords, if it returns 1.
if (results.MoreRecords)
{
// Increment the page number to retrieve the next page.
pageNumber++;
pagingCookie = results.PagingCookie;
}
else
{
// If no more records in the result nodes, exit the loop.
break;
}
}
I personally tend to use LINQ rather than FetchXML, but it's worth noting what Lasse V. Karlsen said, if you are presenting this information to the user, you probably want to be doing some kind of paging (either in FetchXML or LINQ)
You can use LINQ as shown below. The CRM LINQ provider will automatically page the query and run as many requests as is needed to get the full result, and return the complete set in a single object. It's really convenient for us. However, be careful with that. If the result set is very large it will be noticeably slow, and it could even throw an OutOfMemoryException in extreme cases.
public List<Entity> GetEntities(string entityName)
{
OrganizationServiceContext DataContext = new OrganizationServiceContext(ServerConnection.GetOrganizationProxy());
return DataContext.CreateQuery(entityName).toList();
}
Here's an alternative implementation for paging with FetchXML, which I like much better than the official examples:
int page = 1;
EntityCollection entityList = new EntityCollection();
do
{
entityList = Context.RetrieveMultiple(new FetchExpression(String.Format("<fetch version='1.0' page='{1}' paging-cookie='{0}' count='1000' output-format='xml-platform' mapping='logical' distinct='false'> ... </fetch>", SecurityElement.Escape(entityList.PagingCookie), page++)));
// Do something with the results here
}
while (entityList.MoreRecords);
I had the same issue. I solved it by including the id of the entity in fetch xml or Query Expression. If you include pass in "lead" in the query then also add "leadid". Then the paging cookie is auto generated for you.