Skip to main content

The Top Six New CRM Features in Dynamics 365 Version 9.0

December 2017 - Microsoft Dynamics 365 Version 9 includes a number of new features and enhancements in the area of CRM. We have highlighted six you should definitely know about:
1. Unified Client Interface
CRM has become part of Dynamics 365, which means that even the new Office 365 client portal provides clean navigation, crisp layout of fields and grids. A responsive unified interface for the Customer Service Hub and Business Edition applications means that users enjoy the same experience on Mobile and Tablets.
2. Web Client Refresh
The new web client interface has undergone a significant refresh: borders around containers and uniform spacing, more colour theming, field controls styling, font standardisation, and text wrapping fix.
3. Multi-Select Option Sets
Set an option set as multi-select and it renders on forms as an intuitive multi-select control.  Advanced Find has new operators specifically designed for these, plus filtering in Views. The form list is searchable too.
4. Activity Timeline
This feature combines Posts, Activities, and Notes into a single feed.  It also enables you to filter specific activity types and quickly identify un-read items.
5. LinkedIn Sales Navigator
With the LinkedIn Navigator solutions for Sales and Campaigns, you can build on existing LinkedIn functionality to view and synchronise data for your Leads, Accounts, and Contacts. As well as providing quick access to Company and Contact profile data, inMail and messages, tasks, appointments and other activities can also be tracked in Dynamics 365.
6. Virtual Entities
Virtual Entities are similar to traditional entities. However, external data are read at run-time without being stored in the Dynamics 365 database.  This is a great new feature for heavy, custom integrations. As you create an organisation-owned entity, check the metadata box to indicate that it is virtual.

Comments

Popular posts from this blog

Microsoft Dynamics 365 CRM Troubleshooting Solution Import Errors

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...

How to Filter SubGrid Lookup view in Dynamics 365 CRM

How to Filter SubGrid Lookup view in Dynamics 365 CRM.  Please check the comments in the below code and do follow the steps accordingly and call the  filterSubGrid() funtion on onload. var LastQuery = ""; function filterSubGrid() { debugger; setSubgridLookupFiltering(); } function AddLookupFilter(entity_type, customFilter) { var subgridLookup = Xrm.Page.getControl("lookup_Contacts_Participants"); subgridLookup.addCustomFilter(customFilter, entity_type); } function setSubgridLookupFiltering() { var subgridAddButtonId = "Contacts_Participants_addImageButton"; //Try to get the element from both the current and the parent document. var subgridAddButton = document.getElementById(subgridAddButtonId) || window.parent.document.getElementById(subgridAddButtonId); //This script may run before the subgrid has been fully loaded on the form. If this is the case, //delay and retry until the subgrid has been loaded. if (subg...

How to prevent record from saving in Dynamics CRM using Javascript

  From time to time you might need to add some validation to the save event of an entity, this actually used to be an approach I would use on a regular basis but since the introduction of business rules have found myself doing this less and less. But still, knowing the ability is available is handy. When you define the onsave event function, you must tick the “Pass execution contact as first parameter” option. (See below) Having done that you can create an onSave function with code similar to the example I have shown below. Note forgetting the “(context)”, which will take the context parameter allowing you to prevent the save when needed. function onSave(context) { var saveEvent = context.getEventArgs(); if (Xrm.Page.getAttribute("telephone1").getValue() == null) { // *** Note: I am using an alert for testing a notification maybe better! alert("Put in a phone number!"); saveEvent.preventDefault(); } } Note: This simple example might be better achi...