Sitecore Computed index and custom fields added only for custom index in multi Azure index Environment

-

We have a requirement to create custom azure index with some computed fields, so I have created the custom index(site_master_index) and added the computed fields, but this sitecore instance is a multi-site, so adding computed field should only needs to be added to my newly created index instead of adding to all the indexes.

Steps followed to create this index and computed field in Azure.

  • Add a patch file for creating computed fields and that will be only added to our newly created index.
  • Create the patch by inheriting from contentSearch/indexConfigurations/defaultCloudIndexConfiguration in the newly created patch file.
<?xml version="1.0"?>

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
            <sitecore>
                        <contentSearch>
                                    <indexConfigurations>
                                                <customSiteConfiguration
                                                            ref="contentSearch/indexConfigurations/defaultCloudIndexConfiguration ">
                                                            <fieldMap ref="contentSearch/indexConfigurations/defaultCloudIndexConfiguration/fieldMap">
                                                                        <fieldNames hint="raw:AddFieldByFieldName">
                                                                                    <field type="System.String" fieldName="title" searchable="YES" retrievable="YES" facetable="YES" filterable="YES" sortable="YES" boost="1f" settingType="Sitecore.ContentSearch.Azure.CloudSearchFieldConfiguration, Sitecore.ContentSearch.Azure" cloudAnalyzer="language"/>
                                                                        </fieldNames>
                                                            </fieldMap>
                                                            <documentOptions type="Sitecore.ContentSearch.Azure.CloudSearchDocumentBuilderOptions,Sitecore.ContentSearch.Azure">
                                                                        <fields hint="raw:AddComputedIndexField">
                                                                                
                                                                                    <field fieldName="thumbnailurl">EMAAR.Emaarcommunities.Foundation.Indexing.ComputedFields.ThumbnailUrl, EMAAR.Emaarcommunities.Foundation.Indexing</field>
                                                                                    <field fieldName="pageurl">EMAAR.Emaarcommunities.Foundation.Indexing.ComputedFields.PageUrl, EMAAR.Emaarcommunities.Foundation.Indexing</field>
                                                                                    <field 
                                                                        </fields>
                                                            </documentOptions>
                                                </customSiteConfiguration>
                                    </indexConfigurations>
                        </contentSearch>  
</sitecore>
</configuration>

  • Create custom index where we need this computed index field to be get added.
  • Add the above defined computed fields to the custom index patch configuration file created.
  • Using ref keyword(inherit) the parameters and settings from the computed index patch file created in the xpath contentSearch/indexConfigurations/customSiteConfiguration
<sitecore role:require="Standalone or ContentManagement" search:require="Azure">
                    <contentSearch>
                              <configuration type="Sitecore.ContentSearch.ContentSearchConfiguration, Sitecore.ContentSearch">
                                        <indexes hint="list:AddIndex">
                                                  <index id="site_master_index" type="Sitecore.ContentSearch.Azure.CloudSearchProviderIndex, Sitecore.ContentSearch.Azure">
                                                            <param desc="name">$(id)</param>
                                                            <param desc="connectionStringName">cloud.search</param>
                                                            <param desc="totalParallelServices">5</param>
                                                            <!-- This initializes index property store. Id has to be set to the index id -->
                                                            <param desc="propertyStore" ref="contentSearch/indexConfigurations/databasePropertyStore" param1="$(id)" />
                                                            <configuration ref="contentSearch/indexConfigurations/customSiteConfiguration" />
                                                            <schemaBuilder ref="contentSearch/searchServiceSchemaBuilder" />
                                                            <searchService type="Sitecore.ContentSearch.Azure.Http.CompositeSearchService, Sitecore.ContentSearch.Azure"/>
                                                            <strategies hint="list:AddStrategy">
                                                                      <!-- NOTE: order of these is controls the execution order -->
                                                                      <strategy ref="contentSearch/indexConfigurations/indexUpdateStrategies/syncMaster" />
                                                            </strategies>
                                                            <commitPolicyExecutor type="Sitecore.ContentSearch.CommitPolicyExecutor, Sitecore.ContentSearch">
                                                                      <policies hint="list:AddCommitPolicy">
                                                                                <policy type="Sitecore.ContentSearch.TimeIntervalCommitPolicy, Sitecore.ContentSearch" />
                                                                                <policy type="Sitecore.ContentSearch.ModificationCountCommitPolicy, Sitecore.ContentSearch">
                                                                                          <Limit>1000</Limit>
                                                                                </policy>
                                                                      </policies>
                                                            </commitPolicyExecutor>
                                                            <locations hint="list:AddCrawler">
                                                                      <crawler type="Sitecore.ContentSearch.SitecoreItemCrawler, Sitecore.ContentSearch">
                                                                                <Database>master</Database>
                                                                                <Root>/sitecore/content/sitecontent</Root>
                                                                      </crawler>
                                                            </locations>
                                                            <enableItemLanguageFallback>false</enableItemLanguageFallback>
                                                            <enableFieldLanguageFallback>false</enableFieldLanguageFallback>
                                                  </index>
                                        </indexes>
                              </configuration>
                    </contentSearch>
          </sitecore>
  • Publish these config files and do indexing from sitecore and then now we will able to see new computed fields created in Azure index.
Note:
Index name should be in lower case.
Happy indexing 😊



Comments

Post a Comment

Popular posts from this blog

Custom Item Url and resolving the item in Sitecore - Buckets

-
Image
I have a situation to update the Item URL to be SEO friendly as my items in content tree looks like below. In the above image in order to resolve the item, Sitecore will find the item from the below URL http://domainname/en/dine/nv/chicken but I need to form a URL that is more SEO friendly like http://domainname/en/chicken In Sitecore by Out of box, we can achieve this by using Aliases , we can create an Aliases under System à Aliases and in the Linked Item field select the target item. But this is very tedious as we need to go to every item in the content tree and create Aliases, instead of that we will be going to do it programmatically using custom pipelines. ·          Link Provider (Provides the custom URL for the item based on the templates) ·          Item Resolver (Resolves the item based on the custom URL generated by CustomLinkProvider , that we going to create later...
Read more

Fixing Sitecore Buckets folder path - Items created after 12 AM server time zone

-
Image
We are working on a 24/7 content publishing site, so it is important to have articles published on the correct date and time.  We are using Sitecore buckets to manage article items. In the Sitecore content tree, when the content author tries to look at the items created after 12 AM server time, the items are created under the previous day folder only,  but it is supposed to be created in the current day folder( ie. new bucket day folder to be created and the items to be added in this new day folder ). We have hosted the site in Azure VM in the UAE region. UAE is 4 hours ahead of GMT/UTC (UTC+04:00) so items created between 12 AM to 4 AM are always created under the previous day's folder, but when the item created after 4 AM is properly created under the current day folder in the content tree. Example: If the item was created on 2024 à 09 à 24 between 12 AM to 4 AM then still the item is made under the bucket folder of 2024 à 09 à 23 The created date and the updated ...
Read more

Sitecore Search - API Crawler with Edge Pagination

-
Image
Sitecore Search provides different ways to index the items from 3rd party systems with the help of Source Connectors. There are different types of Source Connectors available: API Crawler API Push Feed Crawler Web Crawler Web Crawler(Advanced) I have provided more details here about the different sources for crawling different types of documents to get indexed into Sitecore Search. In this article, I would like to share the details about API Crawler in more real-time querying data and adding to the index. We have a scenario where I need to index all the items along with their placeholder components based on a specific template that has a layout assigned to it. I decided to utilize the Experience EDGE GraphQL Query to get the data and index it to Sitecore Search. We can use this for non-layout items as well. This article covers the following: GraphQL - Layout Query with Components GraphQL - Item Query GraphQL - Item Query with Pagination GraphQL - Search Query with Pagination Graph...
Read more