Recently I have embarked on a journey to understand further a new function which Microsoft have rolled out with the introduction of the outlook App for CRM their has been challenges in understanding the configuration part which l will write on in my future blog detailing some of the challenges which comes with configuring the outlook app.
In this post l will be writing on the cool function of relevant search.
Microsoft Dynamics 365 App for Outlook is an Office add-in that you can quickly add to your user's outlook applications.
Sow this enables the user's to track emails and appointments, create
contacts, and review Dynamics 365 information in context of their emails or their appointments.
To be eligible for this app, Users will need the Use Dynamics 365 App for Outlook privilege and have server -side synchronization set up for incoming emails or for appointments, Contacts and Tasks.
Microsoft Dynamics 365 App for Outlook uses relevance search. If relevance search is turned on for your organization, make sure that these entity types are searchable: Account, Opportunity, Case, Contact, Lead.
How to enable relevance search in Dynamics 365:
Go to the system settings and set up search then enable the relevance search.
Advantages of the Relevance search:
Relevance Search brings the following enhancements and benefits:
Improves performance with external indexing and Azure Search technology.
Finds matches to any word in the search term in any field in the entity.
Matches may include inflectional words, like “stream”, “streaming”, or “streamed”.
Returns results from all searchable entities in a single list sorted by relevance,
based on factors like number of words matched or their proximity to each other in the text.
Matches in the result list are highlighted.
Relevance Search isn’t available for Dynamics 365 (on-premises) organizations.
Relevance Search is disabled by default. As an administrator you will need to enable it for the organization. After Relevance Search is enabled,you may have to wait up to an hour or more, depending on the size of your organization,before you start seeing the Relevance Search results in the Dynamics 365 web application.
Smaller changes in indexed data may take up to 15 minutes to show up in your system.
While Relevance Search finds matches to any word in the search term in any field in an entity,in Quick Find, even with the full-text search enabled, all words from the search term must be found in one field.
In Relevance Search, the better the match, the higher it appears in the results.
A match has a higher relevancy if more words from the search term are found in close proximity to each other.
The smaller the text where the search words are found, the higher the relevancy.
For example, if you find the search words in a company name and address, it may be a better match than the same words found in a large article,
far apart from each other. Because the results are returned in a single list, you may see a mix of records displayed one after another, such as accounts,
opportunities, leads, and so on.
The matched words in the list are highlighted.
Popular posts from this blog
Microsoft in recent months made available a much requested feature by many with the additional way to access read-only data in Microsoft Dataverse. The TDS endpoint for Microsoft Dataverse allows read-only access to Dataverse for reporting and analytics requirements. The Tabular Data Stream (TDS) Protocol endpoint functionality is managed by an administrator with access to the Admin center. This feature becomes a game changer as many Microsoft customers who required this feature and often went down the root of the Data Export Service can now start exploring this capability Prerequisites: To get started using this feature, you will need to ensure that TDS endpoint is enabled as this is required to be able to use this feature via Power BI or SSMS. Sign into the Power Platform Admin Center :( https://admin.powerplatform.microsoft.com/environments ), and then select the appropriate sandbox environment. Note: Its always good practice to test new features in a Sandbox Environment Validate t
Purpose The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item Audience This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments. Pre-Requisites Dynamics 365 with IFD Configuration Dynamics 365 Update 220.127.116.11 (KB4046795) Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later Office 2016 *Recommended, Office 2013 *Compatible Supported browsers for Outlook on the web Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers: Internet Explorer 10, Internet Explorer 11, or Microsoft Edge The following configuration is supported: Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet. Protected Mode
A Colleague from Microsoft shared their Pre go-live checklist that is used in their Fast-Track program. So here is a copy for you all, and what customers must be prepared to answer before Microsoft is deploying the production environment. 1. Solution acceptance by users: UAT A. Is UAT completed successfully? How many users participated in UAT? B. Did UAT test cases cover entire scope of requirements planned for go-live? C. How many bugs/issues from UAT are still open? D. Any of the open bugs/issues a showstopper for go-live? E. Was UAT done using migrated data? 2. Business signoff: A. Business has signed off after UAT that the solution meets business needs? B. Solution adheres to any company/industry specific compliance (where necessary) C. Training is complete D. All features going live are documented, approved and signed off by customer 3. Performance: A.