<img src="https://secure.leadforensics.com/133892.png" alt="" style="display:none;">

It's interesting just how much the Dynamics CRM platform has changed over the years, specifically in the area of data visualisation. Microsoft has progressively incorporated additional options for us, giving system customisers and developers a broader set of tools to deliver great content-aware visualisations.

To name but a few, these options include: the ability to colour entities and business process flows; Native Dashboards; and integrated visualisations surfacing in PowerBI. Additionally, the ability to modify grid views and incorporate visual queues to a data set, insights and many others are included in the current platform offering.

If we explored all of these tools, we would be here all day. Instead let's focus on one specific feature that was made available since the December 2016 update for Dynamics 365. While only a relatively new feature, it's one I feel has great potential where adopted and used well, and become a key consideration when putting together a Dynamics 365 solution. As a bonus, it's also really cool!

The feature I refer to is the ability to add visual web resource to a data view within your Dynamics environment. What this gives us is a method to introduce a visual key to what was previously just a raw value in a grid column.

By attaching a web resource and a JavaScript library to control what icon is displayed based on values within the data row, there is a considerable amount of benefit to a someone who is interacting with the data on a daily basis.

Once configured, an example can look like this:

This is such a cool feature, and the aim of this post is to dive right in to this functionality to highlight what you can deliver and its limitations, explain how this feature is implemented within the platform based on exploratory testing and also cover some basics of data visualisation and the real use cases for implementing it.

I’ll go into more detail on how to setup and configure this future at the end of the post. If you want instructions to set this up you are welcome to skip to the video further down which goes through the implementation process end to end.

It’s ok, I wont mind, but hopefully you’ll stay for the rest of the post too!

Before we dive under the hood and look at this from a technical perspective, it is important to consider the potential impact of this feature and how best to use it to your advantage.

For me the key driver here is the ability to interpret a large dataset, a view in this case, at a glance and build a story from it to make informed decisions.

This is basic data visualisation but there are countless ways of visualising data in Dynamics CRM, so what makes this different? Well, this feature is right at the front line of the system in an area of the product which has a high user interaction and a daily footprint.

Using this feature well, means that our setup is thoughtful and specifically focuses on our ability to focus on highlighted data so that we reduce the time taken to understand data we are presented with.

So if that’s the driver and a key use case for this feature, then should think carefully on how we should be using it and when we customise our Dynamics CRM environments

Views – Under the hood

So how do static views work in CRM? Well there’s a number of components which control how these render and the data that they represent in the application, But there are two very important components that control a View, these are XML data items called:

  • FetchXml
  • LayoutXml

They’re important because these are what we interact with using the out of box customisation tools or via the Software Development Kit (SDK) when creating a new SavedQuery (A View).

If you’ve ever played around with custom filtered lookup with the Client side SDK, you will have interacted with both of these XML configurations. FetchXML may also be familiar to you already if you’ve ever used FetchExpressions to Query data using the SDK, or used the FetchXML builder found in the XRMToolbox

FetchXML

This defines your request to the database (your “query for data”) by specifying which Entity Set you would like to query (eg opportunity), and the fields you would like to be made available on each entity that the query returns in its results. It controls how the data is filtered, and how you want that data to be sorted.

LayoutXML

This controls how the grid represents itself and how the view “looks” in the application. It’s specific to views of data, however the FetchXml is fairly reused within the platform.

Even if this seems a little alien to you at the moment, It is likely that you’ve interacted with these XML settings even if you were not fully aware of it.

If you’ve ever configured a System view, then these two areas are directly affected by the choices you make in view designer.

Below is an example of this, where I’ve separated the controls to highlight which configuration area(s) they interact with.

So actions through the view designer will have direct impact with the XML configuration properties, of the Saved Query once the save button it clicked.

For example, Moving the columns left or right in the designer, will adjust the cell sequence in the Layout XML.

As captured below:

Or, Editing the filter Criteria, to include more view filter options, will effect the Filter elements in the Fetch XML.

Editing Filter Critieria:

Want more information on the end-to-end  implementation process? Watch my guide:

 

Topics

Discuss this post

Recommended posts

Purchase order processing can be a challenging process for many organisations, especially if the approval process you have in place is that of a manual system. Losing paper documents, identifying who has approved what, by which date and why can be one of many a frustration for those who work within the purchasing department.
Making Tax Digital (MTD) is the process of streamlining HMRC returns and it is mandatory for all VAT registered businesses. This is not entirely news, but with only 12% of organisations, the deadline for Making Tax Digital is getting closer and businesses should start getting compliant the sooner, the better! To properly understand the impact of Making Tax Digital, I have interviewed our SME finance expert, Sandra Addison, who has shared her views, concerns and advice on this very debated topic.
As many of us wind down for the festive season, now is a great time to think about the maintenance of the systems your business relies on, and get organised for next year. Next year, we see new trends emerging including Evergreen updates for Microsoft Dynamics 365, so use the end of the year to ensure you are prepared for changes to come.
It works for you. Your employees are comfortable using it. You know what you pay for. But the trouble is, you haven’t updated that software platform in a long time. So long in fact that the vendor has stopped supporting the version your business relies on. No harm in that, right? Wrong. 96% of outdated software has security issues. Say you just bought your dream car - would you park your car without locking the doors? So why then, would you leave the engine of your business unlocked and unsecured? The systems you use to run your business are every bit as valuable as the tangible assets you hold dear. Here are 3 of the dangers of running old software: 1. Security It is no surprise that security tops our list. Outdated systems leave you open to cyber attacks, security breaches and vulnerability in the systems you run. 2. Competitive Disadvantage Unsupported or outdated software also leaves you at a competitive disadvantage, as new features and functionalities are not being added to the versions you are running. 3. Unpredictable increase in cost With your systems not up-to-date you’re running the risk of incurring unwieldy costs not just when something goes wrong, but also when your staff are working with inefficient software that effectively slows them down and costs you more. So, with every reason to ensure you are using an up-to-date platform, how do you ensure you don’t miss an update? Welcome to Evergreen updates Back in 2009, PriceWaterhouseCoopers coined the phrase ‘Evergreen IT’, defining this as standardised resources shared across the enterprise that are scalable to multiple users and flexible to changing demands, without disrupting the entire technology base each time. Microsoft refined PWC’s definition and revised it to be ‘running services comprised of components that are always up-to-date’. [1] In much the same way you are familiar with continuous improvement processes in your organisation, staying on top of your software’s updates can be seen as an incremental business improvement. Software providers like Microsoft will work to similar Kaizen processes as your own business, seeking feedback on their systems; improving the efficiency of the platform; and evolving the software to the benefit of the end user in an incremental way. Evergreen updates for Microsoft Dynamics 365 Upgrades can be an expensive activity, so managing the process in an efficient manner that reduces business risk has always been an imperative for anyone responsible for the lifecycle of a key business application – the time is fast approaching when having a slick process for deploying the latest and greatest software to your workforce will be essential. From April 1 2019, if you are a Dynamics 365 for Finance and Operations customer, your application will become subject to mandatory updates which will be automatically applied to your production system in a timeslot of your choosing. This is good news, right? Yes… it means that all the dangers we’ve discussed around security, costs, and competitiveness are solved in one foul swoop. The problems you have had in the past relating to keeping your business software up to date are solved at a stroke. Not the same as Office 365 You may be used to Microsoft’s Evergreen updates with Office 365. While they are both Microsoft products, the nuances of the change to Evergreen are not the same. You’ll want to be 100% sure that your application, which has potentially been customised, will still function as expected following your chosen patch date. How to manage this process So, are you wondering how you’ll manage this process? Download our guide Evergreen updates for Dynamics 365 Finance & Operations today and start putting in place your plan of action to be ready for these changes when they arrive in April 2019.
One of the biggest challenges for a business when implementing an Enterprise Resource Planning (ERP) solution is not realising the need for organisational change management. Implementing an ERP solution in your organisation implies change and change inevitably will engender some resistance.
right-arrow share search phone phone-filled menu filter envelope envelope-filled close checkmark caret-down arrow-up arrow-right arrow-left arrow-down