Hi,

We have a commerce solution which caters for multiple language, we have a request from client where we have to write our custom cms search provider.

Commerce version is 8.5 and Episerver cms is 7.5

On our solution there are metafields and these metafields are marked for multilanguage to be True. And these metafields are mapped against few of the metalcasses and not all.

What I found from the profiler the stored procedure ecf_CatalogEntrySearch is not utilizing _Localization. There is a bit of sql which is commented as shown below

set @Query_tmp = 'select META.ObjectId as ''Key'', 100 as ''Rank'' from ' + @TableName_tmp + ' META' -- INNER JOIN ' + @TableName_tmp + '_Localization LOC ON META.ObjectId = LOC.Id'

I have to modify the store procedure to include Localization

set @Query_tmp = 'select META.ObjectId as ''Key'', 100 as ''Rank'' from ' + @TableName_tmp + ' META INNER JOIN ' + @TableName_tmp + '_Localization LOC ON META.ObjectId = LOC.ObjectId'

After modifying the above sql it returns the result. Not sure if the commenting of the _Locationzation bit is intended. Obviously the modified sql missing the check for table exist, which is covered on my procedure. 

My C# code is as follows 

CatalogSearchParameters parms = new CatalogSearchParameters();
parms.OrderByClause = "CatalogEntry.Name";
//parms.Language = "en-gb";

CatalogSearchOptions options = new CatalogSearchOptions
{
	CacheResults = cacheResults,
        RecordsToRetrieve = pageSize,
        CacheTimeout = cacheTimeout
};

options.Namespace = "Mediachase.Commerce.Catalog";
options.Classes.Add("AProductPage");
options.Classes.Add("BProductPage");
options.Classes.Add("CProductPage");

string sqlMetaWhereClause = string.Format(@"Loc.OurMetaField like '%{0}%'", keyword);
parms.SqlMetaWhereClause = sqlMetaWhereClause;
return CatalogContext.Current.FindItems(parms, options, new CatalogEntryResponseGroup(CatalogEntryResponseGroup.ResponseGroup.CatalogEntryFull));

In the above code the multi language MetaField (which is OurMetaField) is found in AProductPage_Localization, BProductPage_Localization, CProductPage_Localization.

Can some one confirm if they faced the similar problem, or any solution without modifying the stored procedure.

Thanks,

Rams