Dynamics 365 Field Service

Since single byte and double byte are existing in Japanese language, it is difficult let user to set single byte of special character as mandatory in just search in our operation.

Also in user operation, our user are unable to convinced why need to input the character which is not included in work they want to search.

Under the situation, would like to request to remove inputting " * " from general search, but only with word user wants to search.

Usually, our operator in dealer is using this whenever need to contact particular opportunity, order or such using customer description, vehicle registration number or such, and if exact description or number is needed for search, they need to check and recognize those form 100% in any database or document in advance to search it.

For example. for search with customer description, they need to clearly input correct byte, correct space and correct special characters such as registered in DB in case of search with Equal. Especially for the byte, it is quite critical in Japanese language that several single byte and double byte are mixed up in the description as Customers applied.

Under the situation, Equal is not used at all in search, but Contains is used as most frequent in our dealer.

At the moment you have to activate "show assets" on the new pcf for functional location tree every time you want to check the functional locations assets. It would be great to be able to default this option to being checked (or not)

At the universal ressource scheduling we can more less customize all forms and views except the "Create Booking" form.

We have the requirement to add an option set to the booking during the scheduling process. Therefore we ask for the ability to customize also the "Create Booking" form.

Currently, RSO schedules all available resource requirements to a resource based on the defined scheduling criteria.

In a scenario where there a more requirements than resources, this leads to a fully booked schedule with no availability.

Consequence of this is that all maintenance work orders are scheduled as soon as they are created, and service work orders created from cases cannot be scheduled anymore, because there is no availability.

The idea consists creating various capacity bands, where a percentage of the total available capacity can be allocated to certain work orders. This may vary based on customer type, work order type, or asset type. This needs to be flexible to variate in the allocation of capacity throughout different time periods in the year.

With this, RSO will reschedule the bookings and requirements according to the defined scheduling rules, but only limit this to the set capacity for the defined time window. Refer to the list below as an example:

Type of Work Capacity % Winter Capacity % summer

Maintenance 20 50

Repairs 50 30

Repair High Prio 15 10

Customer Group 1 5 10

Total 100% 100%

Type of work

The number of capacity bands should be unlimited, as long as the total adds up to 100%. The time from/to window should be flexible in dates. Capacity

Concern:

When dispatcher creates a booking in Daily view, if the resource already had a booking, the booking is split into 2 bookings which requires dispatcher to update the booking (by right click the booking > Edit > edit the time). Initially when dispatcher creates a booking in Daily view, there is no option to set the time of the booking and the booking will be created with start time = resource’s start time, which leads to the scenario.

The goal is to prevent multiple bookings from being created for a single work order when customer's scheduler drags and drops it on the schedule board. 

Issue Details:

Duplicate booking records are generated for a Work Order, all having the same "Created On" date, whenever the Scheduler drags and drops the Work Order on the schedule board.

Concern:

When dispatcher creates a booking in Daily view, if the resource already had a booking, the booking is split into 2 bookings which requires dispatcher to update the booking (by right click the booking > Edit > edit the time). Initially when dispatcher creates a booking in Daily view, there is no option to set the time of the booking and the booking will be created with start time = resource’s start time, which leads to the scenario.

The goal is to prevent multiple bookings from being created for a single work order when customer's scheduler drags and drops it on the schedule board. 

Issue Details:

 Duplicate booking records are generated for a Work Order, all having the same "Created On" date, whenever the Scheduler drags and drops the Work Order on the schedule board as per screenshot below.

On the Schedule Board screen, it might be very useful to connect the filters applied to the Requirements pane (on the bottom) with the map. For example, if there are 100 requirements and, after applying a filter the pane shows only 20 items, the map should show only the 20 requirement's locations just filtered

When planning Bookable Resource daily tasks,the system calculates travel times between Start Location and the first activity address and then among each activities. Is it possible to add also calculate and show on the Schedule Board the travel time from the last activity of the day and the End Location?

It might help the planner to understand how far is the last activity of the day from the location where the technician needs to return and if the time needed is within his working hours or not.

Would it be possible to add a Dark Mode option to all pages within Dynamics 365? Most people have Dark Mode on everything else. Hurts the eyes when i go to dynamics throughout my day. Thank you!