Posts

Showing posts from March, 2019

Dynamics Multi Entity Search (Global Search) Entity Selection Using C#

Image
While coming up with deployment scripts i was tasked to ensure that the Dynamics Global Search had specific entities selected.  By utilizing one the undocumented SDK message i was able to set this data. ( list of undocumented messages ) The manual way of updating these settings 1. Navigate to Settings -> Administration -> System Settings 2. Click on the button for Select entities for categories search 3. Add/Remove the entities you want utilizing the selection screen. How to do it utilizing code: var request = new OrganizationRequest("SaveEntityGroupConfiguration"); //create a new QuickFindCofigurationCollection var qfCollection = new QuickFindConfigurationCollection(); //add the entities you want to include in Global Search qfCollection.Add(new QuickFindConfiguration("contact")); qfCollection.Add(new QuickFindConfiguration("incident")); //set the parameters for the request. It took several hours and digging through the //CRM Sdk

Filter Customer Id field on Case Entity To Only Show Contacts or Accounts

Recently while working on a project where the customer was utilizing the Case entity they wanted to only allow users to enter contacts into the Customer Id field. In order to achieve this you first need ensure that the pre-search only shows contacts.  Next we need to ensure that if the user clicks the "Look up more records" link they only see the option for Contacts in the Look For drop down. Note : In order to change this to only show Accounts just change all the references to "contact" or "contactid" to "account" and "accountid" respectively. //attach our filtering code to the customerid field Xrm.Page.getControl("customerid").addPreSearch(filterCustomerField); function filterCustomerField() { //This filter ensures that no accounts will be returned since the accountid field is never null var customerContactFilter = " "; Xrm.Page.getControl("customerid").addCustomFilter(customerContactFilter,

Exporting Duplicate Detection Rules Using CRM Configuration Migration (Data Migration Tool)

Image
In order to move Duplicate Detection Rules to another system utilizing the CRM Configuration Migration tool make sure to add the Duplicate Detection Rule and Duplicate Rule Condition entities to the Schema. VERY IMPORTANT NOTE!: Before you try to export the records you have to Unpublish the rules otherwise the tool will skip exporting all the Duplicate Detection Rules and just export the Duplicate Rule Conditions causing you import to fail.