You’re offline. This is a read only version of the page.
Announcements
10
Hi All,
I'm wondering if others experience the same issue as we do. Let me explain:
We have a "vanilla"-instance of Dynamics 365 CE with Field Service. This environment is without any additions, customizations or adjustment of settings. We store a new "msdyn_workorder" (or "bookableresourcebooking") in it, via “Dynamics 365 Customer Engagement Web API” (Odata-Interface). The call we use is "POST /api/data/v9.1/msdyn_workorders". We don't do anything special when saving the msdyn_workorder.
This action will take 2 to 8 seconds. This is way too long, should be under 200ms (we think). Saving these entities really takes much longer than other entities. That is always the case and not incidentally.
In the image below there is an Azure logging. This shows different calls to the environment with the time it takes. The call to "POST /api/data/v9.1/msdyn_workorders" takes almost 8 secs!
We also see this slowness when we do this via the normal UI, only it is a bit more difficult to measure (This can be seen in the last two images).
We see this in all Field Service environments, so not just in this one.
What causes this? Could this be due to a Microsoft plugin?
What is acceptable? How long should a typical call take in a standard environment?
We noticed something else. If we do the saving every minute, it takes less time on average (about 2 sec, still too long). But if the intervals become longer (to an hour), the saving also takes longer (it will be 8 seconds). In normal use, the last interval will be the most likely. The other calls are fast so the environment is not asleep (or something like that).
Hi Terpstry,
You are welcome.
If I answer your question then please mark it as verified.
Let me know if I can provide you with more details.
Thanks
Regards,
Abdul Wahab
Power Platform & Customer Engagement Developer/Lead/Solution Architecture/Project Manager
Direct/WhatsApp:+923323281237
E-mail: abdulwahabubit@outlook.com
Skype: abdul.wahabubit
Linkedin: www.linkedin.com/.../
Hi Terpstry,
As the work order is one of the main tables of the Field Service application and it has a lot of logic besides. I think this may be the reason for this performance issue.
You can do one thing, analyse the whole work order table and the features you are not using right now. Turn them off. for example, if a plugin is doing something specific and you do not need this specific feature then turn it off.
For a detailed analysation of this performance issue. You should open the ticket with Microsoft. This will give the exact details.
If I answer your question then please mark it as verified.
Let me know if I can provide you with more details.
Thanks
Regards,
Abdul Wahab
Power Platform & Customer Engagement Developer/Lead/Solution Architecture/Project Manager
Direct/WhatsApp:+923323281237
E-mail: abdulwahabubit@outlook.com
Skype: abdul.wahabubit
Linkedin: www.linkedin.com/.../
#1
André Arnaud de Cal...
294,110
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
