I have blogged a few times about capabilities around service level agreements (SLAs) within Dynamics 365 Customer Service! This time I plan to cover a specific requirement that frequently arises …. as we often need to understand the impact on our SLA when re-opening a resolved case.
I recently saw a “trick” with Dynamics 365 that I thought was quite cool. So, I decided to document it in a blog post. This must be a reasonably common scenario! Our sales team want to purge the system of some old contacts. They were given a spreadsheet listing all the existing data. And people marked the ones that needed to be deleted. Great! But how do I easily remove these contacts from our Dynamics 365 instance.
I have recently been asked to review the new real-time marketing feature. I have therefore been busy testing its capabilities and comparing real-time marketing and outbound marketing. This post will include my initial findings and thoughts.
Dynamics 365 now includes several Teams collaboration options, one being the ability to enable chats directly inside Dynamics 365. In this video I demo how to use and setup this new feature.
Within Dynamics 365 we can use SLAs in the customer service app. Each SLA item can trigger a Power Automate Cloud Flow to complete any actions we wish to implement when a warning, failure, or success status is reached. This is great but I’ve found maintaining the Flows can become cumbersome. In this post I will explain an alternative approach.
I had a really simple requirement the other day but it took me time to work out the solution! So I thought I would describe my challenge and the solution …. in an attempt to help others. In this post I will explain how to create a view of records shared with from an access team.
I haven’t blogged about JavaScript or code changes for some time! Probably because in Microsoft Dynamics 365 I mainly use a low code approach these days. But today I had a small challenge with some code and thought the solution I found might be useful to others ….. my challenge was that my business rules weren’t being triggered after a field had been changed using JavaScript.
Out of the box it is pretty easy to create a two stage SLA with Dynamics 365. This is great as often we have a need for a service level agreement that relates to “First Response By” and “Resolve By”. But occasionally a requirement comes up for a third stage to our SLA, typically something like “Resolution Planned By”. I recently needed to configure exactly this for a customer and thought it might be useful to document the process.
Microsoft have published a tool to help us migrate service level agreements (SLAs) created in the old web client to the newer style SLAs we find in the Unified Interface. In this blog post I will explain what is involved.
I recently got asked a simple question but one I didn’t immediately know the answer for! As I had to research the answer I thought a blog post might help anyone who is presented with a similar question. That being …. “In the Dynamics 365 App for Outlook we can track emails as being regarding a standard set of entities. What if we want a remove entities from this list or add custom ones?”.
Microsoft Dynamics 365 