Suggested by David Wakeman – Completed
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 in conversation with Jason Cohen on Yammer:
•Toggle for "Update End Time" (Y/N) on the Booking Status
•Toggle for "Update Actual Arrival Time" (Y/N)
•Toggle for "Update Start Time" (Y/N)
•Toggle for "Pause Booking Journal"
•Toggle for "Resume Booking Journal"
•Toggle for "Split Booking when applied - Complete previous, create copy with new set as scheduled for right now"
The problem is that the End Date/Time maps that value into the Work Order, Schedule Board and Invoice and which can lead to incorrect invoicing amounts and incorrect visibility in the Schedule Board
I just want the option to have this setting so we don't have to implement complex workarounds
Thanks,
Dave
Status Details
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
Hi,
I think by implementing this without a toggle microsoft are causing issues. I am interested if other users have tested wave 2?
My view which i emailed through:
I do need to challenge the described logic and please pass my direct feedback to the Product Team. If there is a more formal way you would like me to pass it on, please let me know.
The request itself from the customer in the URL provided showed they wanted a Y/N toggle. They are simply trying to fix an issue where if they go in to correct a booking that has failed from 2 days ago or was not completed by the Resource 2 days ago when they should have completed, they didn’t want the end time updated to current time. That is where the schedule board looks incorrect and invoicing is incorrect. That small % issue is fixed with this change.
However I believe by not introducing the toggle as requested, Microsoft have fixed 1 minor issue, and introduced several usability issues and taken away something that was working perfectly.
I expect once other customers realise how this works in PROD, they will complain.
If a work order is completed earlier than planned, the schedule board still has the work order going over the original time. Same if a work order takes longer than planned.
Invoicing would also be incorrect.
I strongly believe Microsoft have misinterpreted the idea from the customer and are introducing more issues than they are solving. The toggle is the key and it was not introduced with the change. Below is the original post I can find for the idea.
The update worked in our dev environment but is not working in UAT after Wave 2 deployment.
Trying Field Service app update to see if that resolves the issue before deploying wave 2 in production.