Introduction With new release of Microsoft Teams, CloudFronts decided to analyse and check if Teams could be used for communication within the organization and we figured out few points between Yammer and Teams as which tool can be used as the best to enhance the communication within and outside the organization. Following are some points on Yammer and Microsoft Teams based on different key points. # Yammer Microsoft Teams Basic Idea – Yammer is like Forum Discussions – Especially used for Asynchronous Communication – User Interface is like Company Facebook – Chat Group- Real Time Conversations – No external/guest access – Integration with third party services Support – Discontinued the Desktop Client but Mobile App Available – Available on both Desktop Client and Mobile Client. Mobility – Supported on Android, iOS, Windows phone – Supported on iOS, Android phones Multimedia Support – No Audio, Video Conferencing – Supports both Audio and Video Conferencing External access – External groups feature in Yammer enables us to extend and makes it easier for External teams to work together. – Integrates with Office 365 Groups. CRM Integration – Yammer can replace the Activity Feeds solution in your Microsoft Dynamics CRM Online organization, though your Activity Feeds components will remain in the same state they were before installing Yammer. Yammer simply replaces Activity Feeds in the users’ workspace. – No integration with CRM. Praise /Polls – With Yammer Users can do announcements, praise and have poll. – Microsoft Teams does not provide functionality to have praise and polls. Alerts /Notification – Posts in Yammer can be notified via Emails (Personal Settings) – Notification appears only when we chat (Desktop App). Whereas there is no intimation when users post in Channels though the channel name is highlighted in bold. Meeting Invites/ Calendar – – With Teams users can schedule, view and update their Meetings and can view Calendar from Teams. They also highlight the number of attendees who have accepted the Meeting. Connectors – – Teams can be connected to Third Party Installers. For Developers Team can connect to Yammer, TFS etc. – TFS can help the Development Team to organize the task and see the status and manage them easily within the Team Window. Additional Points – Files uploaded on Yammer stays in Yammer and are not uploaded in SharePoint or OneDrive. But Files from OneDrive can be added in the post on Yammer. – Yammer, you can search for public groups and ask to join them. In Yammer, you have private groups which cannot be seen at all. – Microsoft Teams is Business Casual – No outside people can be added to the conversation. – Teams is built on top of all of the existing Microsoft technologies. Under the hood, every Team is actually an Office 365 Group – When the user is creating or uploading the files in the team it is actually uploading and creating files in SharePoint – T-Bot is a training bot at this time. It’s designed to allow you to ask questions and get a quick reply on how to complete a particular task. – In Teams, you only see the Teams in which you have been invited to. Conclusion – Yammer is the social network – Yammer is a bulletin board for the entire organization – Teams is the social interaction with fresh UI. – Teams works well asynchronously, for more informal, Business Casual conversation. Conclusion Thus, we at CloudFronts use Yammer to connect to External Groups but Microsoft Teams for our internal communications and awaiting more enhancements in Team in near future.

Overview: At CloudFronts, we use our Dynamics 365 PM App to track and manage Projects with Task and Resource Scheduling, Project Billing and Invoicing, Timesheets, Gantt Chart, Time and Expense Entries, User Skillsets and many additional features. We recently implemented an intelligent time entry reminder notification workflow to intimate users about pending time entries with the goal of establishing a culture of doing time entries on a daily basis. Why do we need this? A Professional Services company relies on team members who contribute to billable entries which in turn helps the company estimate Project Costs, Forecast Revenue and most importantly ensure billing is done on time and accurately. High Level Flow Diagram The below image shows the diagrammatic representation of high level flow of what we implemented. Custom Logic The Custom Workflow logic has series of steps that checks and based on the conditions it sends out email to that particular User. Check if it’s a Weekend As the step name suggests, this will check if today is a Saturday or Sunday and if the condition is true the workflow will stop. Check if it’s a Public Holiday If current day is not a weekend, there is a possibility that it might be a public holiday. So in this step it checks if today is a Public holiday. If true, then the workflow stops. Get Previous Working Day This step fetches the Previous Working Day as in if today is Monday then the previous working day in our case is Friday. Else if Tuesday then, previous working day is Monday. Check if the Previous Working day is Public Holiday Now there might be the case, that the previous working day was a Public holiday then in that case the time entries will not be there for the users. So if the Previous Working day is a Public Holiday then the workflow stops. Fetch Users This step will get the users who enter time entries in the system, be it a billable resource or a non-billable resource. Fetch Time Entries Here in this step, fetch the time entries less than 8 hours. If we have complete 8 hours’ time entry, then no alert is sent to that particular user. Else if we have incomplete time entries then the next step is to check if the user was on Leave. Is User on Leave? If we have less than 8 hours’ time entry, then there is a possibility where that person was on leave on the previous working day. In that case no reminder will be sent to that particular user. Send Email With the above criteria’s and conditions, if we get that user was working and has not completed his/her daily time entry, then an alert will be sent to that user. So with this simple logic and series of steps, CloudFronts was able to achieve this and intimate their users to complete their time entries.

Introduction: Document Recommendations are one of the preview feature that is added in Dynamics 365. In this blog let’s see how we can enhance the use of this feature in our Business Requirement. Note: Since it’s a preview feature, it is advised not to use and it is subject to change. So not recommended on Production Environment. Pre- Requisites Document Recommendations are supported on Dynamics 365 Online. Since it’s a preview feature the System Administrator needs to enable this from Settings -> Administration -> System Settings -> Previews Tab. User should have access to SharePoint Online 2013 or SharePoint Online 2016 for Document Repository. Document Management must be done before hand i.e. enabling SharePoint or OneDrive for Business. Relevance Search should be enabled. Azure Text Analytics can be used optionally to determine the Document Suggestions. System Administrator must define the similarity rules. Working Suppose we have a Sales Representative and Sales Manager that is working with Opportunity in D365 and all documents related to this are associated with this particular Opportunity. Now another Sales Representative starts working on this Opportunity and she is unaware with all the previous details and deals. So with Document Recommendations, CRM provides her with all the documents to understand about previous conversations, assets and makes it easier for the new Sales Representative to work with this particular Opportunity. Now the question is how this works? So there are certain prerequisites that are required to establish this feature. Configuration Enable Document Recommendations Enable SharePoint Settings -> Document Management -> Enable SharePoint Online. Enable Relevance Search Configure Similarity Rules Create Similarity Rules Similarity Rules can be created from Settings -> Data Management -> Similar Records Suggestions Settings ->New Rule as shown in the first image. While the second image shows how to configure rule.  So when we create a new rule below are some details that System Administrator needs to fill. Source Entity – For which entity the rule is enabled. Document Recommendations is supported only for COLAC Entities (Case, Opportunity, Lead, Account and Contact) + Custom Entity. Filter results by Status – Whether it is Open, Won or Lost in case of Opportunity and different in the case of other entities. Use Text Analytics – Yes or No. By Default, the value is No but then if using Cognitive Service Text Analytics then set the value to Yes. Maximum Number of Key Phrases – this is used to determine the keywords or key phrases to determine with text search which helps to achieve key word based similarity between source and target records. The acceptable value is from 0-1000. Create Match Fields Once the Similarity Rules are created the next step is to create the Match Fields, so on Similarity Rules a sub-grid is present to display all the Match Fields. Match Fields involves the following details. Criteria – Whether it should be Exact Match or Text Match. In Exact Match, fields from the source entity is matched. In Text Match, text in these fields are used to find the key phrases. Entity – Choose an entity to use in creating a text search rule to find the matching records. Fields – Select a field to find the matching target records. To enable field for Exact Match, the field should be added in Quick Find View of that particular Entity. Once the Match Fields are created, simply activate the Similarity Rule. Manage Document Suggestions Document Suggestions can be managed under Settings -> Document Management -> Manage Document Suggestions. Once we open this setting we can only see the list of entities for which the similarity rules are listed. We can also provide the External Base URL for querying the results as shown in the images below. Example So based on above steps, I tried Document Suggestions on my trial environment and below screenshots will demonstrate the same. Here I have created Similarity Rule for Opportunity Entity and document recommendations will be displayed for the records. So I have created two different Opportunities, to buy IPhone 7 and IPhone7s and I have added the documents regarding the deal cracked for buying IPhone 7 so when I view suggestions for IPhone 7s it will show the related documents associated with IPhone 7 on Document Associated Grid of Opportunity to Buy IPhone 7s. The above screen shot shows that since the topic name had similar key words that’s the reason I could see the recommendations. This happened due to Similarity Rule created where in Match Fields I had declared the Text Match of the Field “Topic” on Opportunity. Also Document Recommendations will read documents stored in SharePoint Online, OneDrive for Business or Office 365 Groups. Document Recommendations is not supported in Offline Mode. Whereas on Mobile/ Tablet Clients the recommendations will be shown as shown below.  

D365 field service or Dynamics 365 for field service is one complete field service management software. It is a product from Microsoft. It helps large and medium businesses to become quite efficient. This software can hold stuff such as service agreements, service locations, customer assets, preventive maintenance, resource management, work order management and so forth. You will have total control over your field service management teams. The scheduling options available on this software is quite flexible. You can significantly boost customer service when you use this particular ERP solution.  So many excellent features are available in this particular ERP solution. Integrating the Outlook calendar with the field service is entirely possible when you are using this ERP suite.  Introduction: This blog explains how to configure work order bookings for Field technicians who need them to show in the Outlook calendar. Prerequisites: 1. Dynamics 365 Field Service licenses 2. Office 365 Enterprise E3 licenses Configuration: Enable and Test email mailbox for relevant Users is successful. Working: Below are steps for setting up Outlook Integration with Field Service to set this up in the system Login to Dynamics 365 Field Service environment as an “Administrator”. Next, go to Settings > Administration > System Settings > Synchronization and check Synchronize resource bookings with Outlook. Login to Dynamics 365 Field Service environment as a “Technician”. Navigate to Options > Synchronization. And check Synchronize resource bookings with Outlook. Login to Dynamics 365 Field Service environment as an “Administrator” and schedule a Work Order to Technician. Login into Outlook with the User related to that “Field technician”. Open Calendar and booking is shown as below. Note: The Booking may take 10+ minutes to show in Outlook. This is because it is an asynchronous service.  

Customer service is the backbone of any organization. Any company that desires to progress or scale-up high should focus on providing the best customer service to their clients. But, with so many things happening at the same time, it is pretty tough to provide it. Hence, it is wise to use  Dynamics 365 customer service, an ERP solution. It will not only help you to become effective but, it will help you and your team to be more efficient. Since it is cloud-based software, you get information from your team in real-time.  The best part about this particular enterprise resource planning software is that it offers a host of different features. For example, ‘Voice of Customer Survey,’ is one of those salient features that you will love using.  Voice of Customer is a feature of Dynamics CRM where you can create and send out surveys to gain valuable feedback from your customers about your products or services. Respondents can take your surveys on a phone, tablet, or computer. Anonymous surveys can be triggered in different ways: Email Social sites like Twitter, Facebook or other web pages SMS In this blog, we will discuss how we can achieve sending surveys using SMS. We had a requirement for the client that whenever work order status is changed to completed, send a survey SMS to the contact to fill out the feedback for the service provided. Pre Requisites: Voice of Customer Solution installed Power SMS solution. Download Power SMS from here- http://www.powerobjects.com/powerpacks/powersms/ Choose a Service Provider CallFire(for US numbers) Twilio Configuring Power SMS. The configurations steps can be found in Power SMS User guide here- http://www.powerobjects.com/guides/powersms/. Steps to be followed to send survey using SMS are listed below: Create survey in Voice of the Customer as per your requirement and publish the survey. Create a workflow on work order status field that creates Survey Activity. On creation of survey activity, survey link will be created. Populate and store the survey link in work order contact some custom field on work. Step: Create survey activity Step: Update contact Create a workflow that creates a SMS message on update of survey link field. After creation of SMS, set the status of the survey as “Pending Sent”. Step: Create SMS When a work order status will be changed to completed, SMS will be send using workflow. You can see the status reason whether the SMS send successfully or not. Thus, surveys can be distributed using SMS and feedback can be stored for analysis and improvement of the organization. For more information on Voice of Customer you can refer our blog “Voice of the Customer for Dynamics CRM 2016”.  

In this article, we are going to walk through the pros and cons of Financials feature of ‘Coupling’ which enables integration of records between Financials and Dynamics CRM. This will help customers understand suitability of using out-of-box Integration. Introduction: Out-of-box Integration enables user to integrate and synchronise data in Microsoft Dynamics Financials record types to corresponding Microsoft Dynamics CRM entities. For more detailed information please refer the link: https://www.cloudfronts.com/integrating-microsoft-dynamics-crm-with-microsoft-dynamics-nav/. Pros: 1. Easy Setup: Setting up Financials in CRM requires you to import DynamicsNAVIntegrationSolution and then just to provide the URL for Financials. Setting up CRM in Financials is easy. You just need to fill in few details and you are set for integration! 2. Initial Synchronisation: Initial Run Full Synchronisation starts all default integration jobs for synchronizing Financial record types and Dynamics CRM entities. Run Full Synchronisation integrates: 3. Real- Time Synchronisation: Integrations and Synchronisation are fast and simple. We can even schedule a synchronisation. Scheduled Synchronisation will synchronise modified coupled records. 4. Sales Order Integration: Sales Order is automatically integrated once it is Submitted in CRM. Cons: 1. No Custom Mappings: Currently, out of box integration mapping contains lot less field mapping. We cannot customize field mapping as we cannot access Financials backend. 2. Synchronisation cannot be triggered from CRM: Synchronisation of records can only be triggered form Financials. We can only view the coupled records from CRM; we cannot trigger synchronisation from CRM. 3. Multiple records cannot be synchronised: Once the initial ‘Run full Synchronisation’ is done, records created thereafter must be synchronised one by one. Note: Only Multiple Customers can be created in Financials. 4. Mandatory fields in Financials are not Mapped: There are lot of fields which are not present in CRM but are mandatory in Financials, those field values are not set by Integration. 5. Limited entities can be used for Integration: Not all entities can be used for Integration. Below screenshots displays the Out-of-Box Integration Mapping Table: Conclusion: Out-of-Box Integration in Dynamics 365 Financials is recommended for organisations having simple requirement for Integrations. Additionally, it is cost saving as you don’t need to pay a hundred dollars for a third-party Integration tool for very simple Integrations.

In this blog article, we will explain how to move data from SQL server to Excel file using SQL Server Integration Services (SSIS). For moving data from SQL Server to Excel you need to create package, to import data from SQL Server to Excel. Step 1: – Create a Project You need to create a project for moving data from SQL Server to Excel. For this go to visual studio-> File-> New-> Project Once you click on project then choose a business intelligence option to create SSIS project. Then select Integration Services. And then Click on Integration Server Project. Specify name to the project and then click on OK. Step 2: – Create a Data Flow Task We need to add a data Flow task to control flow tab of your package. After adding the data Flow task double click on it will open the Data flow tab. Step 3: – Creating the SQL Server Source Our aim is to move data from SQL Server to Excel. So here our source is SQL Server and Destination is Excel So, drag and drop the OLE DB Source component from the Source then right click on that component then click on edit. Below window will open. Then click on new Click on new Then select your Server name, Authentication type. Select your database name means from which database you retrieving the data. Then click on Test connection to verify that our connection is right or not. And then click on OK. Again, click on OK. Then select the table from Specified database. You can also verify data by clicking on preview button then click on OK. Step 4: – Creating the Excel Destination Our destination is to put the data in excel file. So, drag and drop the Excel destination component from the Destination. Then click on OLE DB Source component and then drag blue line and drop on Excel destination. then right click on that component then click on edit. Below window will open. Then click on new then set the path where you want to create an excel file. Click on OK. Then click on another new button to select the excel sheet name. Click on ok -> ok Then click on drop down bar choose excel file then click on mapping. and then OK. Here, your package is ready execute. Before executing the package verify the source and destination. In destination, there created one excel file with name that you specified in earlier in excel destination with no data. For execute a package, go to Solution explorer ->under the project name -> SSIS Packages -> Package.dtsx. Then right click on that .dtsx and the execute package. it will show the number of rows inserted in Destination i.e. in excel file. And then check the destination. All the data is integrated in destination.

Dynamics 365 for finance and operations is an ERP solution that helps you to streamline the processes and helps you to become efficient. ERP stands for enterprise resource planning. It is a cloud-based application that helps the team members to work with each other with ease. This product is developed by Microsoft and is one of the most popular ERP solutions in the world.  Installing and using this application is not that difficult. If you put in some effort, you will quickly learn how to use this system with ease. You will get to enjoy so many awesome features when you use this particular ERP suite. If you are a new user, it might take some time before you understand how to navigate or do certain tasks in it.  In this blog article, we will see how we can integrate attachments to and from Dynamics 365 Operations. We need to create a Data Entity which will be general for integrating all attachments to other systems. Attached data will be passed in the Attachment field and transferred in Byte Array format. Prerequisites: D3fO Environment. Steps: Create new Project. Duplicate the Entity Make the Entity general for attachments. Build and Synchronize the Project. Create a new project Open Visual Studio. Go to File -> New -> Project. Select Operations Project. Provide a Project Name and Solution Name. Click OK. Duplicate the ‘EcoResDocumentAttachmentEntity’ Entity Go to AOT -> Data Model -> Data Entities -> EcoResDocumentAttachmentEntity. Right Click EcoResDocumentAttachmentEntity -> Duplicate in project. Make the Entity general for attachments. Change Entity Property. Delete EcoResProductImage DataSource Go to Data Source -> Docuref DataSource -> EcoResProductImage. Right Click EcoResProductImage -> Delete. Delete fields Change Entity name in methods Go to Methods. Press F7. Replace EcoResDocumentAttachmentEntity with new Entity Name. Build and Synchronize the Project. Build the Project and Synchronize the Database. So, this will create an entity to integrate attachments to and from D3fO. Let me know your reviews. I will soon come up with more articles, as I further explore D365 Operations.  

Introduction: Microsoft Dynamics CRM entities can be integrated with Microsoft Dynamics NAV out-of-the-box using the default integration setup which is available in Microsoft Dynamics NAV. The Default integration setup has to be enabled to perform integration. This enables users to integrate and synchronize data in Microsoft Dynamics CRM entities such as accounts, contacts, products, user, transaction currency, Sales Order and unit group with equivalent record types in Microsoft Dynamics NAV such as customers, contacts, items, Salesperson, Currency, Sales Order and Unit of measure, respectively. Pre-requisite: Microsoft Dynamics CRM Microsoft Dynamics NAV Purpose: In this article, steps to perform integration between Microsoft Dynamics CRM and Microsoft Dynamics NAV will be provided using the default integration setup. Steps: To perform Integration between Microsoft Dynamics CRM and Microsoft Dynamics NAV, Coupling equivalent records types is the first step which has to be setup initially. Microsoft Dynamics CRM records can be coupled with Microsoft Dynamics NAV records – essentially linking the records together. Once coupled, you can access Microsoft Dynamics CRM records from Microsoft Dynamics NAV and, for some entities, access Microsoft Dynamics NAV records from Microsoft Dynamics CRM. Import the solution in Microsoft Dynamics CRM of Microsoft Dynamics NAV integration which is present in the NAV DVD. Fig 1: Microsoft Dynamics NAV integration solution imported in CRM Enter the Dynamics NAV URL in ‘New Dynamics NAV connection’ present in CRM. Fig 2: New Dynamics NAV connection in CRM Now in Dynamics NAV navigate to Microsoft Dynamics CRM Connection Setup. Enter the Dynamics NAV URL and other credentails to enable Dynamics CRM Integration. Enable integration by checking the Enabled checkbox. Fig 3: Microsoft Dynamics CRM Connection Setup in NAV. Enter the Dynamics NAV Web Client URL. Enable Sales order Integration Fig 4: Enable Microsoft Dynamics CRM Sales order integration Fig 5: Pre-requisites to enable CRM-NAV integration Now under actions tab, click on ‘Use Default Synchronization setup’ and ‘Synchronize modified records’. Synchronization copies data between Microsoft Dynamics CRM entities and Microsoft Dynamics NAV record types (tables). Hence, Microsoft Dynamics CRM and Microsoft Dynamics NAV Integration is now enabled. A coupling provides the basis for integrating records in Microsoft Dynamics CRM with records in Microsoft Dynamics NAV. Essentially a coupling associates or links a Microsoft Dynamics CRM record to a Microsoft Dynamics NAV record. Hence, coupling has to be setup for integration. If you want to synchronize data in the account in Microsoft Dynamics CRM and the customer in Microsoft Dynamics NAV, set the Synchronize After Couplingfield to one of the following options: Yes – Use the Dynamics NAV Data Copies the data from mapped fields of the customer in Microsoft Dynamics NAV to the account in Microsoft Dynamics CRM. Yes – Use the Dynamics CRM Data Copies the data from mapped fields of the account in Microsoft Dynamics CRM to the customer in Microsoft Dynamics NAV. Couple CRM users to NAV Salespeople. Navigate to Salespeople in Microsoft Dynamics NAV. Fig 6: Couple CRM users to NAV salespeople. NAV Salesperson Bart Duncan is coupled with CRM user Tina Menezes Couple CRM accounts to NAV customers. Note: Before coupling NAV customer and CRM account, the salesperson code of the customer must be coupled to a Dynamics CRM user. Fig 7: NAV customer ‘Selangorian Ltd.’ is coupled with CRM account ‘Adventure Works’. Once coupled, Opportunities, Quotes and Cases of the CRM account appear beside the coupled NAV customer as shown below. Also, in CRM for the corresponding coupled account, NAV account statistics will be visible which shows the NAV customer to which this CRM account is coupled. Couple CRM Units Groups to NAV Unit of Measures. Navigate to NAV Unit of Measures. Setup coupling with CRM unit group. Fig 8: Unit of measure in NAV Fig 9: NAV Unit of measure ‘PCS’ is coupled with CRM Unit Group ‘NAV PCS’ Couple Dynamics NAV currency with Dynamics CRM transaction Currency. Fig 10: Dynamics NAV Currency ‘USD’ is coupled with Dynamics CRM Transaction Currency ‘USD’ Couple CRM products to NAV items. Fig 11: Dynamics NAV Item ‘1001’ is coupled with Dynamics CRM product ’12 inch Security Monitor’ Sales Order Integration When sales order is just created, it does not appear in Navision. As the sales order is submitted it appears in Navision. After a sales order is created in Microsoft Dynamics NAV, you can modify the sales order in Microsoft Dynamics NAV. Fig 12: Sales order ‘Test order’ created in CRM – Status changed to submitted After submitting sales order, in the search box of NAV enter Sales Orders, and then choose the related link. In the Sales Orders window, on the Navigate tab, in the Dynamics CRM group, choose Sales Order List. The Microsoft Dynamics CRM Sales Orders windows opens to display a list of only sales orders in Microsoft Dynamics CRM that have the Submitted status. Fig 13: Submitted sales order from CRM appears in NAV When you post a sales order in Microsoft Dynamics NAV, the status of the coupled sales order in Microsoft Dynamics CRM changes from Submitted to Invoiced. Conclusion: Integration between Microsoft Dynamics CRM and Microsoft Dynamics NAV provides the following capabilities: Enables users to work in both Microsoft Dynamics CRM and Microsoft Dynamics NAV. Users can view data for equivalent records, such as Microsoft Dynamics NAV customers and Microsoft Dynamics CRM accounts from either system. Data can be shared and synchronized between Microsoft Dynamics CRM and Microsoft Dynamics NAV. This enables users to keep information up-to-date in both applications.

Introduction: Relevance Search brings the Global Search Experience powered by Azure Search. It uses scoring concepts where score is the indicator of the item’s relevance i.e. higher the score, more relevant the item. Users will get the comprehensive search results quickly in a single list that is sorted by relevance. How it Work’s Basically when a user looks for something like “Nancy ran in the retail store in New York”, the search is executed against the Azure Search Index and the results are returned with a match to any word present inside that particular sentence. This search will also look for the inflectional words like in our case words like running, run, runner and then will display the results accordingly. No wild cards are required to search anywhere in the text. Enhancements in Dynamics 365 Earlier Relevance Search was enabled only in web Browser but now it is enabled for Mobile Client i.e. on Mobile and Tablets. Explore results using Filters and Facets Global Facets Users will be able to see the refined search by Record Type based on following categories like Entity, Owner, Modified On and Created On. These categories cannot be changed as they are predefined by the system as shown in the leftmost image shown below. Entity Specific Facets When user clicks on particular record type such as Account, then user can see the additional facets specified for that particular entity as shown in the rightmost image attached below in our case Primary Contact and Industry. These Entity Level Facets are customizable based on the personal choice i.e. they can facet fields that they would like to see for every searchable entity in their Personal Options. Search within the Documents in Dynamics 365 Relevance Search will now search within the documents that are attached in Notes on a particular record. Relevance Search will also search in the attachments that are added in the Email in CRM. Search in the records that are being shared with you Search in the text of Option set and Lookup fields on any entity. Set Up and Configuration Enable Relevance Search Only System Administrators can enable Relevance Search. Configure Fields in Quick Find View The fields that are added in Quick Find View becomes the part of External Search Index. There is no limit on how many searchable fields can be added for a particular entity. However, there is a limit on total number of indexed fields i.e. maximum of 1000 fields can be added in an organization. Set Managed Properties System Customizer needs to check the managed properties on the entity. As the “Can Enable sync to External Search Index” option must be true. Configure Entities for Relevance Search The System Customizer can add entities that should be enabled for external searching in the Default Solution. So when a user selects the entity, the number in the parentheses indicates the number of fields of entity that will be synced to external search index shown in image below. Below the progress bar of Total Fields shows the percentage of indexed fields to maximum number of fields allowed of searchable fields. Configure Facets and Filters Facets and Filters refines the search in the organization. They are available on the left hand side of the pane immediately after user searches for some term. As mentioned above they can be customized based on the personal requirements. They can be configured from the Personal Settings as shown in the images given below. Drop down list contains the entities that are enabled for Relevance Search. And for a particular entity up to four facets fields can be selected accordingly. Users can modify the preference of the fields based on their choice. Key Take Away Relevance Search is only available for Dynamics 365 Online and now on Mobile Clients too. By Default, Relevance Search is disabled and can be enabled only by System Administrator. Enabling Relevance Search has no impact on the storage consumption and cost for Dynamics 365 database. Facets and Filters can be configured according the User Preference and can redefine the search as per the user’s personal choice. Thus, above are some highlights for Relevance Search in Dynamics 365.