Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The search result is not always sorted correctly when you use the CatalogSearch object to search a catalog in Commerce Server 2007

FIX: The search result is not always sorted correctly when you use the CatalogSearch object to search a catalog in Commerce Server 2007

View products that this article applies to.

Symptoms

Consider the following scenario. In Microsoft Commerce Server 2007, you use the CatalogSearch object to search a catalog. The sorted column that is set by using the SortProperty property of the CatalogSearchOptions object contains a null value in the data table. In this scenario, the search result is not always sorted correctly.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

This hotfix requires Commerce Server 2007 to be installed on the server because of file dependencies.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Catalogcreate.sql Not Applicable1,121,29015-Mar-200718:12Not Applicable
Categoryresults.sqlNot Applicable12,25127-Feb-200703:58Not Applicable

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

After you apply this hotfix, all the new catalogs that are created return the sorted result. To resolve this problem in the existing catalogs, you must run the Categoryresults.sql scripts in the existing catalog databases.

Steps to reproduce the problem

To reproduce the problem, use the following code. 
CatalogServiceAgent agent = new CatalogServiceAgent(@"http://localhost/catalogwebservice/catalogwebservice.asmx");
            CatalogContext ctxt = CatalogContext.Create(agent);
            CatalogSearch srch = ctxt.GetCatalogSearch();
            CatalogSearchOptions srchOptions = srch.SearchOptions;
            InventoryOptions invOptions = srch.InventoryOptions;
            invOptions.FilterBackorderableSkus = false;
            invOptions.FilterOutOfStockSkus = false;
            invOptions.FilterPreorderableSkus = false;
            invOptions.PropertiesToReturn = "";
            srchOptions.ClassTypes = CatalogClassTypes.AllClassTypesClass;
            srchOptions.PropertiesToReturn = "";
            srchOptions.RecordsToRetrieve = 1000;
            srchOptions.SetPaging(1, 1000);
            srchOptions.SortDescending = false;
            srchOptions.SortProperty = "MyProductId";
            srchOptions.StartingRecord = 1;
            srch.AdvancedFreeTextSearchPhrase = "\"duplicate*\" and \"productname *\"";
            srch.FreeTextSearchPhrase = "";
            srch.SqlWhereClause = "";
            srch.Language = "en-US";
            srch.UseAdvancedFreeTextSearch = true;
            srch.CatalogNames = "SearchTestCatalog1";
            srch.CategoryName = "Category2";
            srch.Recursive = true;
            CatalogItemsDataSet ds = srch.Search();
            GridView1.DataSource = ds.CatalogItems;
            GridView1.DataBind();
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684� Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: KB932827, kbqfe, kbexpertiseinter, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 932827
Revision : 3
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 396