The number of search results that is returned is 5,000 when you set the "Count" attribute to 20,000 in Microsoft Dynamics CRM 3.0 (911510)
The information in this article applies to:
- Microsoft CRM 3.0
- Microsoft CRM Software Development Kit, when used with:
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows registry SYMPTOMSYou use the Count attribute in the FetchXml schema to create a query against the Microsoft Dynamics CRM 3.0 database. Then, you set the Count attribute to 20,000. In this scenario, the number of search results that is returned is 5,000. Additionally, the SELECT statement in the SQL language is always SELECT TOP 5001 regardless of what is set for the Count attribute and for the Paging attribute.CAUSEThis issue occurs when you use the FetchXml schema to retrieve a resulting search set and when the moreRecords attribute is set to 1. The value of 1 indicates that more than 5,000 records are available. In Microsoft Dynamics CRM 3.0, the Paging attribute has a page limit of 5,000.RESOLUTIONMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. To resolve this issue, use the Paging attribute to retrieve records. Then, use the moreRecords attribute in the resulting search set to determine whether the next page should be returned. For example, the following code demonstrates how to resolve this issue.
moreRecords = true;
i = 0;
while(moreRecords)
{
get page i
if(result has more records)
i++
else
moreRecords = false
}
Modification Type: | Major | Last Reviewed: | 9/14/2006 |
---|
Keywords: | kbtshoot kbExpertiseInter kbMSCCSearch kbMBSMigrate kbprb KB911510 kbAudEndUser |
---|
|