-
Allow Product Name Translation Changes through UI
At present the only way we are aware of to load Product Name translations is through the admin area. This is time consuming and cumbersome for a small number of new translations. It would be far easier if the Names of Products could be update by changing the user language and then changing the translated name if it exists from within the UI Form or View for Products. If the translated name did not already exist it would be good for it to be added to the system through this method. The system currently knows you are trying to edit the translation but shows an error instead of updating the translation. -
Selection of Multiple Territories in Work Order Summary insights
It is only possible to select 1 territory at a time in the Work Order Summary report. It would be useful to be able to select multiple territories, and if the selected territory is a parent to show data from all children/grand chilcdren etc in the report. -
Increases number of relationships allowed in Mobile Offline profile
There is currently a restriction on the number of relationships allowed of 10. This is providing very restrictive as we move to refine the 'Notes' entity. The standard filtering of notes created in last x days is not suitable as a technician may want to view notes created 12 months ago on a Customer asset, but only last 6 months on a Contact or Account. The number of notes currently being synchronized to mobile offline is excessive for us so we need to be able to filter it down by table, based upon Bookings that the technician has +/- 7 days. -
Prevent Active Directory updates from overwriting latitude and longitude data on user
We have had Resource User latitude and longitude data overwritten in D365 Field Service twice now as the address held in the Active Directory is not the actual home address of a technician but an office address. The actual latitude and longitude data had been loaded into D365 but it was overwritten by the geocoded data from the user AD address. Active Directory does not contain latitude and longitude data, only an address. We would see advantage is being able to disable the auto geociding in the user record to prevent these data overwrites. Or as an alternative to include latitude and longitude data in the Resource record and use that instead which would be more versatile as it would allow better scheduling of non user resources. -
Word Template to use Product Name Language Translations
Word Templates created for Work Orders are used to create documents to send to end users a Work Document.
When this template includes Work Order Products and Work Order Services, these have Product Names included. The Product Names have Translations loaded in the different languages in the system, but these translations are not used in the Word Template population.
The Word Template is populated with the Product Name for the language of the User that creates the Word Template.
Each Word Template has a language field on it, so this language should be used to populate the Product Name into the Word Document that is created.
In this way a user can create and issue documents to customers in other languages than their user language. A user can be working in German, but need to issue documents to French speaking customers for example.
-
Allow the Inventory level warnings to be disabled when adding Work Order Products
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.
-
Ability to set or save the Schedule Assistant 'Mode' to Gantt or List
The Schedule Assistant resets the 'Mode' that the suggested Resources and Times to List,
The Gantt view is often preferred by users as it is easier to use, which means very often as soon as the Schedule Assistant window opens, the user will click on the Gantt mode.
Suggestion is to:
- Automatically save the last setting used by the user;
- Ability to set the default for the environment.
-
Allow a record to be deleted with offline data in Mobile Offline enabled
With the Mobile app (standard Field Service Mobile Power App) it is not possible to delete a record.
The issue is not security permissions.
Users such as technicians sometimes need to delete a Work Order Product or Work Order Service for example. When offline is enabled, it is not possible to delete any records through the mobile app.
-
Do not update Work Order 'System Status' when the sub-status is changed and System Status is not different
The current system behaviour is that when a Work Order Sub-status is updated on a Work Order, the System Status value is updated even if it is not different to the existing value.
This causes multiple triggers of Processes and Flows that are triggered by the change of the System Status field in the Work Order entity.
Our use case is that we have 2 x sub-status records with System Status = Posted.
- Issued for Invoicing - default value
- Invoiced - updated later by data
When the 'Invoiced' sub-status is set, all Processes and Flows that are triggered by System Status = Posted are re-triggered, and the Closed On, and Closed By fields are also updated.
We do not believe these fields should be updated, as they were already set.
The requested change is that when a sub-status lookup is changed on a Work Order record, IF the System Status of the new Sub-status is the same as the existing Work Order (System Status) then the System Status value should not be re-written as it is not changed.
It is not possible to set a direct filtered trigger in a Flow based on a sub-status value as it is a lookup.
-
Stop Booking Duration being extended when estimated travel time is replaced with actual travel time
The default system behaviour when a Booking has an Estimated Travel Duration is that the total Booking duration is made up of the planned Work duration and the Estimated Travel Duration.
When the Resource travels to the customer after setting the Booking Status to Travelling, and then sets the Booking Status to In-progress, the Booking duration is being extended by the original estimated travel duration.
The End Time of the Booking is therefore changed to the planned End Time to be the End Time plus another section of Travel.
This can lead to a Booking showing over 2 days in the Agenda view in mobile which is confusing for technicians.
Idea - to change the standard behaviour is this situation to not add the estimated Travel duration to the overall Booking duration at the end of the initial Travel phase.
A setting option to allow existing behaviour may be beneficial for some, although it would be an easy localised customization to automatically add to the Booking Duration with the Initial Travel Duration when the Booking is set to In-Progress. To do the opposite with the existing setup is not so simple as estimated Travel duration gets set to 0 when the Booking is set to In-Progress. This is also strange as it prevents data reporting of estimated travel duration compared to actual travel duration.
You’re offline. This is a read only version of the page.
