Provide work hour and expense recording in Field Service. (Same like in PSA.)
PSA provides a great work hour and expense recording tool for resources.
A lot of customers are asking for the same functionality in Field Service!
We use the same resource entities, schedule Board in both products. Why it is not possible to record work hours and expenses re...
Toggle for "Update End Time" (Y/N) on the Booking Status
The current design of the BRB entity Booking Status updating the End Date/Time impacts our situation of wanting to complete a Booking with the Scheduled End Date/Time values. Currently when you complete a booking, it over-writes the End Date/Time value with a current datestamps Suggestion raised...
Thanks again for raising this item. We've implemented the most critical part of this feedback. Our new default behavior is that when a user updates a booking status to “Completed” on behalf of an assigned resource, the booking’s end time will be preserved and the end-time will not update to the current time stamp.
Complete bookings while preserving end time
Thanks,
Jason Cohen & Valerie Horvath
PMs - Dynamics 365 Field Service
Add Two-Option field to Service Task entity to indocate completed
Most organizations consider work order service tasks as either complete, on not complete, which would be better represented by a two-option field as opposed to a percentage.
Add a two-option field to the Work Order Service Task entity and set the percentage field to 100 when the value ...
Icon depicting the hierarchy chart of a customer asset
In classic Web UI it was possible to add an icon depicting the hierarchy chart of a customer asset structure. This way it was pretty obvious for a user to see if a customer asset had sub-assets and could be viewed in a hierarchy. In the new UI, the hierarchy is still available, but the icon in...
Thank you for your feedback.
The platform released this feature as part of the functionality in October 2019.
Sincerely,
Jason Cohen
PM, Dynamics 365 Field Service
Problem, Cause and Repair
It is common for Field Service organizations to require the tech capture a problem, cause and Repair code on a work order. These codes are then used to rank solutions from highest to lowest probable fix for any give problem. Cause is often then used to determine chargeability or to make recomm...
In wave 1, 2021 we introduced WO Resolutions. Combined with the existing Incident Type feature, we think this meets the need for this concept. A single work order can have many WO Resolutions which can be related to different Work Order Incidents and Customer Assets. If we're still missing some key capabilities in this area, please reach out and/or raise a new idea to improve the feature.
Thanks, again, David.
- Jason Cohen
PM, Microsoft
Migration tool from Field One Sky to Field Services
Actually many clients are facing the problem to migrate from Field One Sky solution to the Field Services.
In order to solve this problem we need a tool that is able to "transform" and migrate all Field One Sky Data into Field Services.
This will help ALL old clients from Fi...
Thank you for your feedback.
We briefly released such a tool but it was too difficult to use and significantly more complex than expected. Customers and partners would not have been able to navigate the upgrade, unfortunately, so we decommissioned the tool. While I suspect this is not something you continue to need, this will never be made generally available, again.
Sincerely,
Jason Cohen
PM, Dynamics 365 Field Service
Field Service Agreement to cover customer equipment
A number of organisations have Field Service requirement require service agreements to specify the customer equipment which is under the scope of the agreement. For example, the Field Service department provides break/fix for customer assets such as cars, computer equipment, facilities e...
Thank you for your feedback.
We released portions of this Idea as part of the functionality in our Field Service SLA and Field Service Entitlement feature in Field Service v8.x. It isn't tied specifically to an Agreement but we see Agreement, Entitlement, and SLA as parts of the overall Entitlement story within Field Service.
Field Service SLA connects the long-standing SLA feature with the Field Service scheduling logic to drive Arrival time SLA scenarios. We don't yet attempt to auto-apply SLAs based on customer conditions but would welcome new ideas on how this logic should be universally driven in a way that would meet the needs of all customers using the feature. For now, we would rely on customer-specific logic or manual application. Please refer to the following link for more information:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/field-service/sla-work-orders
Field Service Entitlements enables entitlement creation against a Work Order and allows an organization to drive specific pricing logic at the Work Order Product/Service level based on the way the entitlement applies to a given work order. We expect that this initial implementation of Entitlement satisfies a significant portion of your ask and would love new ideas to understand how we might improve it further. The detailed documentation for this feature is coming soon; when it is delivered it will be posted in our Docs.
Thanks for sharing this great idea and please keep your ideas coming.
Sincerely,
Jason Cohen
PM, Microsoft.
Remove the rule to throw error on "End Time cannot be before Estimated Arrival Time"
Currently, there is hard-coded rule to prevent any booking's completion if End Time happens to be before the value (Date/Time) in Estimated Arrival Time. This rule should be optional based on the business use-cases because, in some instances, it is possible for a tech to arrive early and finish t...
Thanks, Ali, for raising this.
If we understand the scenario correctly, it sounds like the system is validating on Estimated Arrival Time even after the work is complete. We agree that this doesn't make sense. While we don't think we need a specific toggle for this validation, we did improve this validation. It makes sense to validate on Estimated Arrival Time while the booking is being scheduled. Once the booking has an Actual Arrival Time value, we no longer validate against the Estimated Arrival Time.
This logic was improved in FS v8.8.42.31.
Thanks, again,
Jason Cohen
PM, Microsoft Dynamics 365 Field Service
Prevent PO creation overwriting address fields
Thank you for your feedback.
We released this change. The system should now only populate this value if there is not an existing value present.
Thanks again for your great feedback and our apologies for not updating this Idea more promptly.
Jason Cohen
PM, Dynamics 365 Field Service
Administrator
Thank you for your feedback.
The Field Service Time Entries capability is in Early Access, now, and will be GA as of April 2020. We're excited for the feature and hope it meets your needs.
At this time, we do not plan to implement Expense functionality.
Time Entry documentation: https://docs.microsoft.com/en-us/dynamics365/field-service/field-service-time-entry
Jason Cohen
PM, Dynamics 365 Field Service