I love it when I’m asked fantastic questions! Recently someone reported a problem whilst using the window.IsUSD command. If you don’t know this is a JavaScript command we can use to see if our code is being run within USD or not. In this post I’ll describe an alternative approach.
I am currently VERY hard at work preparing training material for three courses I’ll be delivering in Australia in August. During my preparation I realised that the logic for displaying associated views in Unified Service Desk was different between the Classic web interface of Dynamics 365 and the newer Unified Interface. In this post I will document how to display an associated view using USD and the Unified Interface. (As I noticed several forum posts with people asking how to achieve this.)
I love it when I find something new in Unified Service Desk! I recently spotted an action I’d not used before whilst experimenting with USD v4.1. SetReplacementParameter. But what does this action do and why would you want to use it?
All browsers are pretty much the same thing, right??? The actual answer to this question is a resounding no! When working with Microsoft’s Unified Service Desk (USD) selecting the “correct” browser for your hosting type can make the difference between a solution that’s fit for purpose and one that is slow and unreliable.
I recently had a requirement to be able to quickly resolve a case in Microsoft’s Unified Service Desk (USD), in the end the solution was really easy but not quite what I expected. Here is my solution ….
In Unified Service Desk I often only want to run actions when a particular tab is open. The problem is users are unpredictable things and they may have closed the tab without me knowing or maybe they never opened it. I could just run all the actions regardless and ignore any errors. But I don’t like doing that and it isn’t an efficient way of designing a solution. So, what so we do?
Here is “take two” of my demo …… it shows how to quickly create a Unified Service Desk application using Microsoft’s new interface standard for Dynamics 365, the Unified Client Interface (UCI).
Recently I have started to work with the new feature with have in Unified Service Desk 3.3 that supports Microsoft’s Unified Client Interface (UCI). As I find differences or tips I will create short blog posts. In this post I will cover how the category or relevance search is loaded in UCI.
With the release of version 3.3 of Unified Service Desk we now have support for the Unified Client Interface (UCI). I have started to experiment with this! In this post I will try to give you an overview of some of the key points I have found which you might want to be aware of.
I recently received a great question about agents scripts and I love answering Unified Service Desk questions! This time the question was about a requirement to switch agents scripts. Here is my answer.
Microsoft Dynamics 365 