vtadas

This does seem like an issue which needs to be investigated. Can you open a
case with Microsoft PSS.

Can you try this alternative

CatalogSearchOptions searchOptions = new CatalogSearchOptions();
CatalogSearch search = new
CatalogSearch(CommerceContext.Current.CatalogSyste m);
search.CatalogNames = catalogName;
search.CategoryName = categoryName;
search.SearchOptions = searchOptions;
search.Recursive = false;
/* Return all categories (i_classtype=1) */
search.SqlWhereClause = @"[CustomProperty] = 1 AND [i_classtype]=1";


--------------------
Thread-Topic: Category Search incorrect after FP1 installed
thread-index: AcRziKIx3Lr/kNHNRF2CbX5xohYFzw==
X-WBNR-Posting-Host: 24.218.145.221
From: "=?Utf-8?B?SmFjayBvZiBhbGwgdHJhZGVzLCBNYXN0ZXIgb2Ygbm9uZQ ==?="
<JackofalltradesMasterofnone@discussions.microsoft .com>
Subject: Category Search incorrect after FP1 installed
Date: Mon, 26 Jul 2004 20:20:14 -0700
Lines: 19
Message-ID: <C61BE0F4-7212-492A-AAF6-453AAAE4D029@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.commerceserver.catalog
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.commerceserver.catalog:4833
X-Tomcat-NG: microsoft.public.commerceserver.catalog

The following search (with the names changed to protect the innocent), only
returned categories that had the custom property set to 1. After installing
FP1, and migrating the catalog, the search is ignoring the SqlWhereClause
and returns all the categories. I tried changing the references in my
project to point at the FP1 assemblies (runtime and shared), but that had
no effect.

Any help would be greatly appreciated.

CatalogSearchOptions searchOptions = new CatalogSearchOptions();
searchOptions.ClassTypes = CatalogClassTypes.CategoryClass;

CatalogSearch search = new
CatalogSearch(CommerceContext.Current.CatalogSyste m);
search.CatalogNames = catalogName;
search.CategoryName = categoryName;
search.SearchOptions = searchOptions;
search.Recursive = false;
search.SqlWhereClause = @"[CustomProperty] = 1";

Sincerely,

Jack
--
CYNIC, n. A blackguard whose faulty vision sees things as they are, not as
they ought to be. Hence the custom among the Scythians of plucking out a
cynic's eyes to improve his vision.


Thanks
Vinayak Tadas
Microsoft
http://blogs.msdn.com/vinayakt

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure! For more info visit http://www.microsoft.com/security. Please
reply to the newsgroups only. Thanks

tonyèŸb±Ë¬²*²hœ®‹(~×(

Test
--
Tony

jack of all trades, master of nonezrjjym­§^°Æ¬µêè~zyجrë,Š‰ìš+¢ÊµÊ&

I figured out why the SqlWhereClause isn't working, but I don't understand why this change was made. The following demonstrates what's going on:

CatalogSearchOptions searchOptions = new CatalogSearchOptions();
searchOptions.ClassTypes = CatalogClassTypes.CategoryClass;
searchOptions.PropertiesToReturn = "CustomProperty";

CatalogSearch search = new CatalogSearch(CommerceContext.Current.CatalogSyste m);
search.CatalogNames = catalogName;
search.CategoryName = categoryName;
search.SearchOptions = searchOptions;
search.Recursive = false;
search.SqlWhereClause = @"[CustomProperty] = 1";

Before FP1:

declare @P1 int
set @P1=0
exec dbo.[ctlg_GetCategoryResults_For_CatalogName_en-US] 0, N'CatalogName', 312752, N'[CustomProperty]', N'[CustomProperty] = 1', N' ', N' ', 1, 2147483646, 1, 1, -1, N' ', N' ', N' ', @P1 output
select @P1

After FP1:

declare @P1 int
set @P1=1
exec dbo.ctlg_GetChildCategories N'CatalogName', N'en-US', N'CatalogName', 312752, 1, 2147483646, N'[CustomProperty]', N' ', 1, @P1 output
select @P1

After FP1 without searchOptions.ClassTypes = CatalogClassTypes.CategoryClass;

declare @P1 int
set @P1=0
exec dbo.[ctlg_GetCategoryResults] N'CatalogName', N'en-US', 0, N'CatalogName', 312752, N'[CustomProperty]', N'[CustomProperty] = 1', N' ', N' ', 1, 2147483646, 1, -1, -1, N' ', N' ', N' ', @P1 output
select @P1

The stored procedure that gets called after FP1 is installed is dependent on setting the class types property in the catalog search options. This doesn't seem to appear in the do***entation, and I'm concerned that there are other changes I may be missing that are also undo***ented.

If you would comment, I'd really appreciate it.

Thanks,

Jack

--
CYNIC, n. A blackguard whose faulty vision sees things as they are, not as they ought to be. Hence the custom among the Scythians of plucking out a cynic's eyes to improve his vision.