{"id":30180,"date":"2021-12-15T11:33:54","date_gmt":"2021-12-15T06:03:54","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=30180"},"modified":"2021-12-15T11:33:54","modified_gmt":"2021-12-15T06:03:54","slug":"configuring-dataverse-search-in-dynamics-365-crm","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2021\/12\/configuring-dataverse-search-in-dynamics-365-crm\/","title":{"rendered":"Configuring Dataverse Search in Dynamics 365 CRM"},"content":{"rendered":"

Introduction:<\/strong><\/p>\n

Recently when I was exploring the searching feature of Dynamics 365 sales, I came across \u201cDataverse Search\u201d feature introduced in 2021 release wave 2.<\/p>\n

Previously \u201cRelevance search\u201d feature was introduced which is now replaced with \u201cDataverse Search\u201d along with some additional features. You can refer our previous blog<\/a> which explains about \u201cRelevance search\u201d and its capability of global intelligent search.<\/p>\n

By enabling \u201cDataverse Search\u201d, all model-driven Power Apps will now have the global search experience with the search bar available on the header of environment.<\/p>\n

Configuring \u201cDataverse Search\u201d<\/strong><\/p>\n

To enable \u201cDataverse Search\u201d simply follow the steps given below:<\/p>\n

1. Navigate to Power Platform Admin Center<\/a>, select the appropriate environment.<\/p>\n

2. Click on the \u201cSettings\u201d\u00e0 In \u201cProduct\u201d area click open \u201cFeatures\u201d section.<\/p>\n

3. Under the \u201cSearch\u201d section, there is an option to turn on the \u201cDataverse Search\u201d.<\/p>\n

4. Click on Save button to save the changes.<\/p>\n

\"Configuring<\/p>\n

5. Once saved, the provisioning index process will start. It will take a while to complete this process.<\/p>\n

\"Configuring<\/p>\n

6. Once completed, \u201cDataverse Search\u201d is enabled.<\/p>\n

By default, there are few system tables that are already included with \u201cDataverse Search\u201d. You can refer this doc<\/a> for list of the entities. You can also add custom table additionally as well.<\/p>\n

Now, navigate to https:\/\/make.powerapps.com\/<\/a> and select the appropriate environment.<\/p>\n

Click on \u201cSolutions\u201d and select the appropriate solution, I have selected \u201cDefault\u201d solution for demonstration.<\/p>\n

Click on \u201cOverview\u201d as shown below:<\/p>\n

\"Configuring<\/p>\n

You will observe \u201cDataverse Search\u201d section on right hand side which provides a quick overview of column indexed used in solution and in environment respectively.<\/p>\n

When you click on \u201cManage search index\u201d, you will have option to select\/deselect the table for \u201cDataverse Search\u201d. You can simply select\/deselect the checkbox besides the table name as shown below:<\/p>\n

\"Configuring<\/p>\n

The progress bar at the bottom shows the percentage of indexed fields as a fraction of the maximum allowed number of searchable fields. As you can see in my scenario it shows \u201c29.89% used (284 of 950)\u201d.<\/p>\n

There is no limit on how many tables you can index for \u201cDataverse search\u201d, but there is a limit on the total number of\u00a0fields<\/strong>\u00a0<\/strong>that can be enabled for \u201cDataverse search\u201d.<\/p>\n

The maximum is 1,000 searchable fields for an organization. Out of these 1,000 fields, up to 50 fields are required by the Dataverse search system, so you can configure up to\u00a0950 searchable fields.<\/p>\n

NOTE<\/strong>: Out of these 1,000 columns, 50 of columns are required by Dataverse search. These 50 fields are common and that are part of every table, by default used in Dataverse search. Some examples of common fields are: \u00a0Name, Created On, Modified On, Status, Status Reason, and Owner etc. Hence total of 950 columns available for configuration as searchable columns for the entire environment.<\/p>\n

Indexing columns in \u201cDataverse search\u201d:<\/strong><\/p>\n

The number of fields indexed for a table is dependent on the tables quick find view. Additionally, some field types are treated as multiple fields while counting in the \u201cDataverse search\u201d index.<\/p>\n

To understand this, I have added table named \u201cRenewable Invoice\u201d and configured the \u201cQuick Find View\u201d. You can verify that the columns count for indexing available is 6 columns as shown below:<\/p>\n

\"Configuring<\/p>\n

This indexing of 6 columns count shown above depends upon quick find view, you can verify \u201cQuick find Active Renewable Invoice\u201d view configured. As for simplicity I have added 1 string, 1 option set and 1 look up field it counted as 6 columns indexing.<\/p>\n

\"Configuring<\/p>\n

While most of the fields take up in count as 1 column there is generally a rule to count the columns, like a string field take up 1 column, an option set of field will take up 2 columns in the search index, while a lookup field will take up 3 columns.<\/p>\n

NOTE<\/strong>: As you can see in above screenshot Name, Created On, Status, Status Reason and Owner though added in \u201cQuick find Active Renewable Invoice\u201d view, it is not counted in indexing as they are by default used in \u201cDataverse Search\u201d.<\/p>\n

\u201cDataverse search\u201d result page:<\/strong><\/p>\n

Similar to \u201cRelevance Search\u201d once you type the keyword and press the \u201cEnter\u201d from keyboard, it will navigate to Search Result page where you can find top results related to the entered keyword. As you can see I have entered \u201citem\u201d keyword and got the below result:<\/p>\n

\"Configuring<\/p>\n

You can find detailed explanation of searching functionality using tables and rows by using in this doc<\/a>.<\/p>\n

Conclusion<\/strong>:<\/p>\n

Dataverse Search is easily configurable feature introduced in 2021 release wave 2 that provides accuracy in searching tables\/rows across the environment.<\/p>\n

\"Export<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction: Recently when I was exploring the searching feature of Dynamics 365 sales, I came across \u201cDataverse Search\u201d feature introduced in 2021 release wave 2. Previously \u201cRelevance search\u201d feature was introduced which is now replaced with \u201cDataverse Search\u201d along with some additional features. You can refer our previous blog which explains about \u201cRelevance search\u201d and\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[2354,2361,65],"tags":[2545],"class_list":["post-30180","post","type-post","status-publish","format-standard","hentry","category-dataverse","category-technical","category-webapi","tag-dataverse-search"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/30180","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=30180"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/30180\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=30180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=30180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=30180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}