Dynamics 365 Field Service

After creating a new resource booking via the quick create form, we clicked on the button "Save and create new". It's supposed to stay on the quick create form but after loading it opens the main form of the resource booking.

Users have added the OOB FS Libraries "FS.BookableResourceBooking.Library.Load" & "FPS.BookableResourceBooking.Library.Load" to Quick Create Form.

Current Behavior:

If these FS Libraries are present, when a user adds the details in Quick create form and clicks on "Save and create New" button, it navigates to Main Bookable resource booking form instead of remaining in quick create form.

Feature ask:

If these FS Libraries are present, when a user adds the details in Quick create form and clicks on "Save and create New" button, the Page should remain in same Quick create form,

It would be nice to be able to order global search by field

Inspection forms in the current form support basic inspections, however are limited in capability.

For example: labels, no group objects with collapsible behaviors, criteria based defaulted values, and calculated values are all not support to name a few.

This makes it difficult to use the product to build complex forms required with offline capability.

Improving the features and UX capabilities of the mobile app would significantly improve field user experience.

Customer wants to create a Report using SSRS, so they are using the connection type “Microsoft Dynamics 365 Fetch” in Visual Studio thru Query Builder wizard , the idea is paste the XML fetch built in an Advanced find in Dynamics CE. In Advanced find is retrieving data  but pasting the same XML in Visual Studio no rows retrieved, user used is a system administrator in both sides.

Any other entity is working fine.

Specific Request: allow msdyn_businessclosure entity to be used in SSRS

We would like to be able to define service territories for resources not based on postal codes, but based on geolocalization functionalities that are already embedded into Field Service. This is because defining a great number of service territories and modifying them purely based on postal codes is extremely tedious, and modifying those service territories, even more so.

Ideally, we would like to be able to draw a polygon on a map to represent the service area of a ressource, and all work orders within that area (determined through longitude and latitude data already available through the geolocalization services within Field Service) would be automatically assigned to this ressource. Being able to represent service territories on a map would also help insure that no service area is left uncovered.

It would be useful to be able to import documents which the business currently uses in paper form / on Word to be used as inspection templates, including making fields dynamic.

The task recorder for RSAT [Regression suite automation tool (RSAT) is only enabled in Finance and HR. Ref: Task recorder resources - Finance & Operations | Dynamics 365 | Microsoft Docs

It has very good capabilities and saves a lot of effort in testing.

Request to please raise priority of this work in team's backlog to have this capability ready for Field service modules.

Field Service 8.8.68.25 added a feature for Use of product out of Stock setting.

This provides the option of a warning or error for the user when adding a Work Order Product.

For environments where the inventory levels are not actively managed it would be useful to have a 3rd option to completely disable the messages to avoid the annoyance of users having a message whenever they add a Work Order Product for an Inventory type Product if the Product Inventory levels are not maintained in D365 Field Service.

In most of our customer's use case scenarios, they will be using the RSO to shuffle around the planning over a period that already contains existing bookings. However, when executing the RSO over a time period that already contains bookings, the current default behavior is that the RSO will adjust the duration of those bookings based on duration specified in the linked requirement.

Most of the time this is behavior is undesired:

• The planner may have manually adjusted the duration of the booking in order to respond to real time developments from the field.
• The requirement may have been planned over multiple days or multiple users. The RSO will now adjust one of the bookings to the full requirement duration, and now the requirement duration may be exceeded.

"But the planner can change the requirement if something changes!". Even if they have the permission to adjust the resource requirement (which isn't always the case), often you don't want to change the actual requirement. And let's also admit that the end user is lazy and/or forgetful so they simply adjust the duration of the booking (because that's what they see in the schedule board) and leave it at that.

This is why we expect the RSO process to never adjust the duration of existing bookings, or at least have an option to make this the default behavior. As long as this is not an option, I couldn’t recommend our customers to purchase a RSO license, as it becomes useless in many cases where it would otherwise have a practical application.

When a work order is created, incident items such as products, services, and service tasks are copied to the order using the "Field Service - Copy Incident Items to Work Order" (LongJobs_CopyIncidentItemsToWorkOrder (number 464)) system job.

The documentation says that the system task is a background process and its duration is not specified. The only thing is that it is written that not immediately, but after a while, the elements will be added to the order.

Is there a way to streamline the process of copying incident items so that items are added as soon as the work order is saved?

Adding the data to work order takes more time when the amount of data is more.