Future Proofing your Implementation and Configuration Part 2 – The Roadmap Question

In Part 1 of “Future Proofing your Implementation and Configuration – The Licensing Question” I covered off a couple things to take into account as far as licensing goes. The next question is around the Microsoft roadmap and a few things both customers and partners need to consider when planning for and implementing Dynamics 365 Customer Engagement.

Let me start with an example It’s 2011 and Partner X has developed a FANTASTIC business process management solution that enables businesses to create and manage sales processes, which in turn effectively promotes governance and sales performance within their sales team. After joining the CRM 2013 preview program, it was realised that out-of-the-box Business Process Flows did a similar job. The functionality created and implemented by partner X was still VERY relevant and provided a brilliant solution to their customers, but would the Business Process Flows replace this? The answer is yes and no.

We see similar scenarios in loads of implementations where partners and customers have implemented functionality utilising ISVs, as well as custom code, and this functionality is matched by something being released by Microsoft in a “Next Version / Release”. So, what do we do? We only know what we know right?

There are a load of resources out there that will give you a certain amount of visibility into future releases to make sure you are not “Double Dev’ing” or buying an ISV product that may be deemed unnecessary in the future…Caveat: If your customer needs the functionality now, it will be up to you to be open and suggest the right solution.

My first go-to resource is the Microsoft Dynamics 365 roadmap site. There is a LOAD of information about what is going to be released in the future releases of Dynamics 365 (the ‘In Development’ tab). It’s a really user friendly site that allows for filtering by application.

Back in the day (up to last year) D365 participants were able to register on the MS Connect website to participate in the D365 preview programmes. Connect has been RETIRED… Many of the services offered by Connect are moving to new tools and services. Check out this post for more information.

A lot of the Connect functionality seems to have moved off to the Dynamics 365 Ideas site where one can present ideas which can be voted on. This is a very smart method of keeping an eye out for functionality that may be expected in the roadmap site, based on input from the D365 community.

I would suggest joining the Dynamics 365 Insider programme and applying to be one of the “Insiders” who will join the previews for the selected applications and feedback based on your findings. The application can be filled out here.

A very reliable source of information can also be some of the direct Microsoft resources available to you. Don’t forget the DynamicsLearning Portal (DLP) and the ‘Blitz’ recordings which highlight upcoming functionality and capability. It’s often also worth your time to reach out to your Partner Development Manager or Partner Technology Strategist if you have these available.

The other method of finding out what may be in the pipeline is to watch the forums and groups on all of the social sites. The Dynamics 365 community is larger than you think and many of the members are active participants in sharing knowledge, enthusiasm, and war stories. Multiple blogs out there (Including this one) really do try to share the Dynamics 365 love. The MVP community also do a fantastic job of sharing what they can with all of us, which really helps.

Honestly, the frequency at which functionality is released is completely dependent on Microsoft, but according to a Mr. James Phillips this release cycle should be more consistent and reliable starting from 1 April 2018. It is best to be open and upfront with your customers about what is coming in the future, as you may want to stagger the delivery cycle to cater for this. If we know we have a delivery roadmap of 1 year with our customer and we know that functionality X is coming in 6 months, we may not want to build anything in the interim and then have to deprecate that functionality… OR you may… The most important thing is to be aware that the functionality will be released and that your customer may want the opportunity to select what is available out the box rather than a custom solution.

In summary, try your best to keep your ear to the ground regarding what is coming in the Microsoft Dynamics 365 roadmap and utilise the tools and services out there to educate yourselves. You may be saving yourself time and your customers’ money!

Part 3 of this article will focus on some of the functional elements in future proofing your implementation and configuration.

Dynamics 365 Saturday Learnings and Overview

Recently Kyle Hill and Chris Huntingford attended the D365 Saturday event in London. Firstly, What an EXCELLENT, well organised event. Thank you to all of the sponsors that invested so much time and money into growing the Dynamics 365 community. It was amazing to see so many D365 community members in one location, getting involved and collaborating. A special shout out to Raz, Mohamed, Janet and the rest of the organisers and MVPs that made this event amazing!

We started the event on Friday with a hackathon hosted by the likes of Jonas Rapp talking about the XRM Toolbox and how it can support all kinds of D365 users in their implementations and management of D365 CE solutions. Good to see functionality like the Sitemap Editor and Plugin Registration tool is still in there. I highly recommend this set of tools and give much respect to all of the contributors 🙂 Check out the list of plugins here.

Ben Vollmer hosted a Connected Field Service (CFS) workshop where attendees were taken through the CFS Setup process and were even given an actual IoT devices to connect to the Azure IoT Hub. level 10 cool!

James Phillips opened the session on Saturday with an excellent talk on Digital Transformation. A few big bombs were dropped such as the Outlook Client deprecation message being deprecated. Good news for the MS customers using this… BUT the focus seems to still be on the App. More information can be found here: CONTINUED SUPPORT FOR THE OUTLOOK CLIENT.

There were some really interesting sessions on the go from a host of different presenters. Some were very technical where as others were fairly business centric. One of the areas of clarity that was demystified by Ben was where and how Dynamics 365 Route Schedule optimisation works. You can grab a copy of the presentation HERE. Thanks for this on Ben 🙂 Gethin & Nick from CafeX ran a number of sessions on the Saturday which showed how to improve customer experience and engage customers in the most efficient ways possible.

Something else that had a massive focus was “Women in Tech” and the ability to generate diversity in our partner teams. This was awesome and it was wonderful to see so many of the ladies in Dynamics at this event 🙂 This is a campaign that should be adopted by as many of the Dynamics partners as possible. In order to promote digital transformation, we have to work differently. Jon Keen did an excellent talk at the end of the day which really highlighted the need for diversity. Those Dynamics Guys fully support this and have actually changed our site URL to “The Dynamics Society” in order to show our support.

All in all, it was a FANTASTIC couple of days and I’m really looking forward to the next one!

Can you future proof your Digital Transformation project?

Based on a recent article by my TDG colleague Chris Huntingford, I started wondering about the over-referenced term of Digital Transformation. Why do we need to hear that term again? Well the reason for it is related to Chris’ article on future-proofing your customisations (and platform) and to the Microsoft Dynamics 365 update cycle.

Think of a typical Dynamics 365 transformation project: they span several years and are vastly complex in nature. So, when you undertake these projects, how do you accommodate the 6-monthly release cycle from Microsoft and the architecting of a future-proof solution? The answer is usually that the solution is architected in a future proof manner but the update cycles are ignored because Microsoft give you a year’s leeway before mandating specific updates.

A multi-year programme of work may be conducted over 3-4 years where the core Dynamics 365 product changes significantly in that time where a situation could be realised where as soon as the customer goes live, they need to immediately start thinking about upgrades and patches rather than bedding down the solution and getting the maximum value out of it.

Is it possible to avoid this? Typically, yes, but it requires a bit of forward thinking on both the Dynamics 365 partner’s and customer’s side. Things like the following should be considered:

  • Realising early time to value by deploying smaller functional pieces rather than entire solutions in one go – no doubt this will get the agile vs waterfall people arguing but simply put, the Microsoft update cycle makes waterfall type projects very difficult to complete effectively.
  • Leveraging accelerators/ISVs and preconfigured solutions wherever possible – most Dynamics partners have several of these that are typically stemmed out of industry best practice. Make sure to evaluate them though and check that they are aligned to the Microsoft roadmap, licensing guide, and future-proofed as Chris suggests.
  • Scope in project time for platform updates and new functionality reviews – this is usually a function for some sort of Design Authority, but too often they get stuck looking at current requests without considering what’s coming in the future. Fundamental platform upgrades should also not come as a surprise and should be catered for well in advance. Microsoft have several early release programs available for this as well as their publicly visible roadmap site.
  • Encourage, enable, and promote consultants and customers to challenge the old ways of thinking in favour of newly available alternatives – this point should ensure that the best possible considerations are achieved and is not meant to be a forum for constant debate with no action. Tough I know, but somewhere a decision needs to be made for better or worse, but at least there will have been some considered conversation around the decision before it is just blindly made because that’s the way things have always been done in the past.

Will the above list provide the illusive silver bullet for ensuring that Digital Transformation projects are always successful and utilising the latest technologies and ways of doing things? The answer I am afraid is no. What it should enable is projects that are more flexible and more capable of realising greater value, earlier, for the customer.

Don’t’ forget that there are also technical aspects around the same topics which are just as important but more relevant for the Dynamics 365 partners and consultants delivering these projects. There is no easy way to go through all of the technical aspects that could and probably would change through the lifetime of a Digital Transformation project, I suggest you have a look at and be aware of the following (if you aren’t already):

  • Flow – this new workflow engine that is sperate from the core Dynamics 365 workflow engine provides a huge amount of power and prebuilt connectors that enable several integrations and extended process to be designed and implemented very rapidly. The per transactions model costing should also ensure that you get maximum value for your spend. Don’t gloss over the fact that PowerApps can use Flow and these PowerApps can be embedded in Power BI dashboards which in turn can be embedded in Dynamics 365 Customer Engagement instance. Why would you care? Well you can create one flow that can be triggered either from Dynamics or from Power BI giving a holistic solution that is easily maintainable and cost effective.
  • The Azure platform all up – this is one of the most crown jewels of the Microsoft empire. Huge amounts of capabilities and all easily available to leverage from your Dynamics 365 Customer Engagement instance. Have a look at these in particularly:
  • Teams – collaboration tools continue to evolve and Microsoft Teams is the latest version that is definitely worth checking out
  • Visual Studio Team Services (VSTS) – one of the core components of most Dynamics 365 projects. Whether it’s a code repository, an Agile backlog facilitator or DevOps facilitator, VSTS is definitely worth investing some time in seeing how you can leverage it.
  • Office 365 E5 – lots of productivity in this one, but check out some of the amazing security stuff that Microsoft also include for you.

Future Proofing your Dynamics 365 implementation and Configuration (Part 1 – The licensing question)

Microsoft Dynamics 365 Customer Engagement is an incredibly versatile platform that can be configured with relative ease. This is both a good and bad thing because often solutions that are implemented descend into configuration anarchy. Yes, it sounds as bad and it is. Imagine a deployment with hundreds of entities, attributes and solutions that are irrelevant or are there for no particular reason. On the other hand, what about loads of old ISV solutions that aren’t being used anymore. As fans of Dynamics 365, I can guarantee that most of us have seen this.

So how does one future proof their implementation? I appreciate the fact that there will be loads of opinions on this matter and there are hundreds of things one could do to manage this process from a business and technical point of view.

One of the big questions during any implementation is whether to utilise what is available out the box or whether to create custom entities and attributes. This is generally based on the scenario and the customer’s requirements. Personally, I prefer to use what is already available as much as possible as there is a load of functionality that you may need to rebuild using workflows and plugins if you go the custom route. IN ADDITION, when Microsoft release updates / upgrades, I know the functionality in my solution will be upgraded correctly and is in line with Microsoft projected functional roadmap. That isn’t to say that Microsoft don’t deprecate functionality. They definitely do!

Now, here is the thing: The licensing model limits us or controls what you can and can’t do as far as the addition of custom entities relevant to the existing functionality. YOU MAY NOT REPLICATE THE FUNCTIONALITY OF STANDARD ENTITIES IN DYNAMICS 365 WITH CUSTOM ENTITIES. If the standard entity is replicated then the user must be licensed appropriately for that standard functionality. This is available in the Licensing and Pricing guide on page 17. THEREFORE, in short… you can create your own “Case” entity, sure… However, you will then need to purchase the Dynamics 365 for Customer Services license for users that will be accessing this entity. This is because it replicates the current and standard case management functionality.

This makes absolute sense. Information on the enterprise-licensing model can be found here in appendix B. This is one of the first documents I generally consult during solution design. Microsoft suggest that configurators utilise what’s available within the standard Dynamics 365 platform so that when core functionality is added to the platform on top of the standard entity set or functional area (marketing, Sales, Service, PSA & Field Service), customers have access to this without having to add additional configuration. As an example, when the entitlements functionality was added to the services module, it linked to the standard case entity and functionality as a standard. Companies that had built their own case functionality had to either move to the standard case management functionality or configure a link to the entitlements.

A second example that I have come across before, which required configuration and was considered future proof was where a customer had several case types, each of which required a large amount of data capture. Instead of adding hundreds of fields to the case form, the case was simply used as the header record and a set of custom entities was created for each of the categories. The core case functionality, such as routing and email-to-case was used and the configuration flexibility of the platform was used to apply a huge level of personalisation from an incident management point of view.

In summary, part of future proofing your configuration is to bear in mind what Microsoft offer as out the box functionality, as well as what the licensing model allows you to do and not to do. Often, this involves an honest and transparent conversation with your customer, which will enable you the ability to educate them in what, is required to implement a robust, performant solution that is as future proof as you can make it. In the next post I will be talking about the Dynamics 365 roadmap and how you can prepare your solution for what’s coming.

D365 Custom Control Framework (CCF)

Microsoft Dynamics 365 Customer Engagement contains some impressive hidden gems in some really cool functionality that really promote a more immersive and interactive user experience. One such gem is the Custom Control Framework or CCF, which enables users the ability to place interactive controls over attributes. This video shows off some of the standard Custom Controls and how to add these to the new Unified User Interface (UUI) forms. It is believed that Microsoft will enable us the ability to create our own custom controls in future releases.

I’d also like to give a shout out to Amandip Dhillon for being a part of the testing of these controls! Awesome job 🙂