Utilize booking time stamps to create work order services
Allow for an association between booking time stamps and work order products (could also associate by incident type). Generate work order services when the booking time stamp is created or have a flag to determine timing to generate. In many implementations clients are not understanding the dis...
Creating Incident Type from a work order
Currently, avenues for incident types are as below. 1. Creating incident type from model-driven app 2. Uploading incident types through importing 3. improving Incident type through AI suggestions While creating a work order for which no specific Incident type is available (consider a situation...
Accessing Work Orders easily in custom workspace
Currently, having a list of work orders in a custom workspace does not allow you to open right into a specific order. Instead, from the list you click the hyperlink to a work order, it opens an intermediate list page outside of the workspace that you then have to click into to open the work order...
Create Work order from Power BI system dashboard
With Power BI report/ dashboard getting enabled as a system dashboard in model-driven apps (in 2020 wave-2 release), field service organizations can make data-driven decisions and generate trackable actions in the form of work orders. Enabling organizations to create work orders directly from Pow...
Display Duration and Duration to Bill fields in hours, not days or minutes
The Field Service application UI converts the time to the highest base time. For example, looking at the editable grid “Work Order Services” Duration To Bill is displayed “3.25 hours” but when you click on it, it shows in minutes, that is "195" However, if you go to Work Order Service form itsel...
Incident Type versioning
Service organisations with extensive Incident Type Service Tasks would benefit hugely from a publishing and versioning process for the Incident Type as part of the standard solution (in terms of audit controls and compliance) 1. Incident Type status (where only "Published" versions are visible t...
Embedded Knowledge Search for Work Order
"Embedded Knowledge Search" in Customer Service feature is good for Field Service engineers. Lots of standard Entities can add "Embedded Knowledge Search", so I'd like to add it on Work Order, too.
Add relationship between Work Order Service Task and Incident Type Service Task
When the Work Order Service Task is generated from Incident Type (OOB logic), the ‘Name’ field (on Work Order Service Task) is populated with Service Task name (Task Type Name) I think in many scenarios it would be better to use Incident Type Service Task name instead. It would be ...
D365 should throw some error/notification if there are any lines which are in estimated state (which will not be considered in invoice as they are not marked as status- used), when the system status for work order is changed to Closed- Posted.
D365 should throw some error/notification if there are any lines which are in estimated state (which will not be considered in invoice as they are not marked as status- used), when the system status for work order is changed to Closed- Posted. Which will enable their technicians/users to put f...
Notification if there are any lines which are in estimated state when the system status for work order is changed to Closed- Posted.
-Uses multiple work order product with line statuses both- used and estimated (they have like 50 lines in it) -As when we close the work order with Status- Closed-posted, it automatically generates invoice, in which only the lines with used line status are involved (which is by design) -Expect...