Dynamics 365 CRM

Microsoft Dynamics CRM, although has support for various kinds of fields to be placed on its forms, it does not provide a rich text editor natively. There are several use cases where a rich text editor would be very useful. One such case is when content from CRM needs to be displayed on web pages. TinyMCE is an awesome HTML editor freely available and extensively used in web applications. So, why not use that and embed in a CRM form? you will have the ability to include the editor on any form for any entity and it will allow our users to add some proper formatting and some extra goodies such as tables and source code without issue. OOB Email Editor: TinyMCE Email Editor: Solution Getting an API Key for TinyMCE First step is, we need an API Key which is provided for free by TinyMCE Go to the link below and ‘Sign up for a free API key’ and sign up as required. https://www.tiny.cloud/get-tiny/ It will ask you for the domain, be sure to enter the prima...

All current version Microsoft Dynamics 365 trials and environments are defaulted to the “ Unified Interface Only ” setting.  This is a good thing since Microsoft Dynamics 365 Unified Interface is here to stay and the previous “ Legacy Web Client ” interface is  deprecated  as of September 2019.  For certain situations where we need to run “ Legacy Web Client ” such as for testing existing setups – how do we enable our “ Legacy Web Client ” interface? Firstly – the setting “ Use Unified Interface only ” is  no longer  listed under the Dynamics 365 Client’s Advanced Settings >> Administration >> System Settings >> General area So where did it go? The “ Use Unified Interface only ” setting is now found in the  Power Platform Admin center ! Here are the steps to navigate to this setting: Open  Power Platform Admin center  >> click Environments >> select the Dynamics 365 environment >> click th...

In Dynamics 365, we can filter lookup fields without writing code. In this post, we will look at an out of the box field example and a custom example. The common out of the box example is filtering a contact based on an account. If we create a new Opportunity, we can see if we look at the Contacts field, we see all contacts in the system: And the same with Accounts: If we were to select an Account or a Contact, it won’t filter the corresponding field. E.g. if we selected 3M as the account, it would be useful if the system only showed us contacts for 3M, but this is not the case. Likewise, selecting a contact that belongs to A Datum Corporation does not filter the account to A Datum Corporation. In order to achieve this, we can use the Related Records Filtering property on the Contact field. Open the form in design view, and select the Contact field, then click Change Properties: You will see Related Records Filtering: Click the checkbox, and select to only sho...

How to disable auto-save for a form If you wish to disable auto-save for specific entity forms, you can do this by adding code to the OnSave event in the entity form. 1. Create a  JavaScript  web resource and add it to the form Enter the following information in the web resource form: Name: preventAutoSave Display Name: Prevent Auto Save Type: Script (JScript) Next to the  Type  field, choose  Text Editor . In the  Source  field, paste the following code (see code box below to copy): function preventAutoSave(econtext) { var eventArgs = econtext.getEventArgs(); if (eventArgs.getSaveMode() == 70 || eventArgs.getSaveMode() == 2) { eventArgs.preventDefault(); } } Add the web resource to the Form 2. Configure the  OnSave  event In the  Form Properties  window, in the  Event Handlers  section, set  Event  to  OnSave . Enter the following in the  Handler Properti...

https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/best-practices/business-logic/include-filtering-attributes-plugin-registration https://crmbook.powerobjects.com/extending-crm/plug-in-development-and-workflow-extensions/plug-ins/registering-and-deploying-plug-ins/

Tip #747: If your view is broken If you followed our  yesterday’s tip  and tried to set up a workflow automatically adding a user to a team, you may have seen the error message: “To use this saved view, you must remove criteria and columns that refer to deleted or non-searchable items.” The fix is fairly straightforward: find the lookup view in customizations, remove the offending column and add back the proper one (Name). If you think that it will never happen to your views then wait until someone pulls out  Xrmtoolbox  and uses View Replicator to create a view referring to non-existing attributes. Refernce:  https://crmtipoftheday.com/747/if-your-view-is-broken/

A solution is a bucket where all the  customization  components of a particular project are stored. Creating a solution helps in moving these components from one environment to another. There are three different types of solutions: default, managed and unmanaged. Default Solution . The out-of-the-box Microsoft Dynamics CRM software as well as the pre-deployment customizations are part of the default solution. You can access a default solution by navigating to  Settings ,  Customizations , and  Customize the system: Unmanaged Solution . The beginning state of solution is the unmanaged solution state. During this phase, you can add, edit, update, remove, delete, and test any of the components of the solution. You also have the ability to create restrictions on the components within the solution. Any number of these unmanaged customized solution components can be associated with any number of unmanaged solutions. Managed Solution.  A managed solution is ...

Remember when CRM life was so much simpler that solutions did not yet exist? If you had separate development and production environments and you wanted to move your customizations, you simply clicked  Export Customizations  and voila! It was done. Those were the days. Nostalgia Warning – in case you’ve forgotten, here’s a screenshot to jog your memory: With CRM 2011, the concept of solutions was introduced, giving us a new set of powers – by picking individual entities, workflows, etc., we now had the ability to group together and move only those customizations we wanted to include in our solution. The next great solutions advancement came with CRM 2016: we can now select specific components within each individual entity – so instead of moving the entire contact entity, for example, we have the option of moving only a certain view or field within the entity. And we can do this without having to hack the xml in the zip file. (By the way, if you want to learn more abou...