How to Inspections in Dynamics 365 Field Service?
|Ali Khan||Mar 2|
This is a curated post to share best resources to explore, understand and use one of most amazing feature of Dynamics 365 platform: Inspections in Field Service. "Inspections" is the only option (other than Customer Voice) in Dynamics 365 for business administrators to design a form, end users to fill it up, and then business users to be able to see responses and analytics.
To understand how Inspections works, we need to explore three basic areas:
How to create an Inspection and how it works with Dynamics 365 Field Service (hint: Work Order Service Tasks)
How can a user fill up data in inspection forms
How to extract and report on inspection responses
For the first and second question, there is no better resource than the following video from Dynamics 365 Field Service channel:
The inspection responses are saved in JSON format but are also de-serialised in Customer Voice tables immediately or at a pre-specified time daily (based on the setting). Following article gives a good primer of how to extract and view inspection responses data:
In a recent project, we encountered two advanced scenarios which we initially thought as curve balls but were later turned out as very easy to implement:
The first one was to cater the requirement of maintaining form versions. For instance, a lot of businesses are conducting Covid related inspections. The requirements around what to capture and the shape & format of same are evolving - and hence the requirement to maintain versions of same Inspection form. This is now inherently supported and the following excellent video from the development team gives good overview of the functionality:
The second scenario was based on a business requirement to create a new cascaded inspection record based on the responses of a first inspection. For example, if an initial inspection related to Work, Health & Safety has a 'no' against a certain question, you may want to immediately create a new inspection for Hazards team to go and inspect. This also turned out to be common requirement and luckily, Shawn Tabor (THE field service expert!) recently wrote an article about the very same requirement using Power Automate flows:
Thanks for reading!
Feel free to share your feedback, I'd love to hear your thoughts 😊
Say hi on Twitter and subscribe here if you'd like to get my new posts (on Dynamics 365, Azure AI and IoT) via email (roughly weekly).