Check our Case Studies for examples of how we've helped various companies realise the benefits of Customer Engagement...
Labels on Dynamics 365 dashboards
Sometimes it’s the little things that make a difference between a good user experience and a bad one.
For example, I created a Dynamics 365 dashboard recently for a customer. This dashboard had a very specific purpose, and therefore I didn’t want to give the users the ability to pick other views on the dashboard. I wanted them to use just the view I specified for each component of the dashboard. No problem. In the dashboard configuration area, I simply turned off the view selector. For the example below I’ve used Accounts as the entity, and assumed I want to use ‘Active Accounts’ as the only available view in the dashboard. (This wasn’t the entity or view in my real world situation, but the same principle applies):
So, my default view is showing in the dashboard:
The problem is that the name of the default view is not shown. Not a great user experience.
So, to fix this, I go back to my dashboard and change the ‘View Selector’ option to ‘Show Selected Views’ and then select only my default view of ‘Active Accounts’ from the list:
Now when I check my dashboard, it shows this:
OK, so now the name of the view is showing. This is good. This is what we want. However, there is a dropdown next to the view name. The users will no doubt select this dropdown and be presented with this:
Again, not a great user experience. A dropdown suggests there are other options. To show a dropdown and then show that there are no other options could annoy users.
So, I go back to my dashboard and turn the ‘View Selector’ off again. But this time, I change the ‘Label’ for this dashboard component from the default of ‘Accounts’ to ‘Active Accounts’, and I select ‘Display label on the Dashboard’. Please note, the label here is not the dashboard name, but the label for the specific component of the dashboard:
Now when I check my dashboard, the label is showing and there’s no dropdown:
A much better user experience all round.
This works equally well on system and personal dashboards.
One word of caution. Hard coding the name of the view into the dashboard like this does mean that if you decided to change the view name later, you would have to remember to change it in the dashboard. However, since changing view names is not a very common occurrence, this risk seems low.
Happy CRMing everyone!
The OA Systems development team has a really detailed understanding of every layer of our businessAyla Hutton, Technology and Projects Manager at Safety ‘n Action
Level 1/95 Ascot Avenue
We are always looking for people who are excellent and passionate at what they do to join our team. If this sounds like you then we'd love to hear from you!