You’re offline. This is a read only version of the page.
117
From the documentation:
Time entries are only automatically created for work order bookings and not for independent bookings or bookings related to other entities such as cases or custom entities.
What is the rational for this limitation?
Since Time Entries are created based on Booking Timestamps when a Booking is completed and synced, we can not account for time spent on non-workorder Bookings. Since this time does not get billed to a customer, creating workorders creates unnecessary overhead. We still want to account for this time though as technicians get paid for this time.
I was hoping to let the OOB behavior to do all the work and just have the Field Service Mobile app (Xamarin) create the Time stamps, but these got rejected by the server during sync.
I think my next attempt is probably using a flow triggered by a completed Booking and create time entries based on start/end/actual arrival time.
What is the recommended path to create time entries for these Bookings?
Best Regards
From a field service standpoint, we understand the work order lifecycle and what work order/booking states are used that make sense to trigger timestamp creation. But once it isnt a work order, the product doesnt have knowledge of when to auto create records. So you are on the right path where you either enter manually or create flows/custom logic to trigger automatically when bookings are not related to work orders. If any partners have advice that would be great to pile onto this thread!
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (