Dynamics 365 Field Service

Instead of booking a single appointment, allow scheduling a series of appointments with time range limitations between them (i.e. inspection must be between 5-10 days after the surgery). In order to book all appointments in the series at once the popup to select a time slot should be "wizard like" and show the list of appointments that await scheduling and then allow scheduling them one after the other, with logic to show the allowed time range for each appointment.

Enable synchronization of work orders from the Field Service calendar to the Outlook calendar. This feature would help technicians and other field service personnel by providing a unified view of their schedules across platforms, reducing the risk of scheduling conflicts and improving planning efficiency.

Can there be a way to identify dates a resource is scheduled via the calendar monthly view?

Expected behavior - when user looks at calendar monthly view, there is a visual identifier on the days they are scheduled. I.e. in the month of february, I am scheduled the 10th-15th, and the 29th. As a user, it would be beneficial instead of scrolling the agenda list to see from high level I am scheduled those dates.

The requirement panel in the schedule board does not support grouping, like OOB in Dynamics.

If your view filtering contains a 1:N relationship, it will show more lines of the same requirement.

Eg.

1 resource requirement > related to

1 workorder > related to

3> records of a custom entity

gives 3 lines in stead of 1 line expected and shown in the view.

Field Service Mobile app does not benefit from a desktop browser's ability to use spell check, which leads to technicians leaving grammatically incorrect notes in the system.

enhance inventory management by ensuring that products returned through the RMA (Return Merchandise Authorization) process are automatically flagged as Not Available in the warehouse inventory if they are broken or defective. This ensures that returned products are not mistakenly restocked for sale or dispatch until they are inspected and repaired. The product can be manually updated to Available once it has been repaired and is ready for use.

Detailed Requirements:

• Automatic Status Change on RMA Completion:
• When a product is returned by a customer through the RMA process and is booked back into the warehouse inventory, the system will automatically flag the product as Not Available. This reflects that the product, having been returned, may require inspection or repair.
• The product will still be booked into the warehouse for tracking purposes, but it will be flagged as Not Available and therefore excluded from inventory that can be sold or dispatched.
• Warehouse Integration:
• Once a product is returned and booked into the warehouse as part of the RMA process, it will:
• Automatically be marked as Not Available, ensuring it is held in inventory but not immediately available for use, sale, or dispatch.
• The warehouse or repair team will inspect and, if necessary, repair the returned product.
• Manual Update to Available Status:
• After inspection and any necessary repairs are completed, warehouse staff can manually update the product’s status from Not Available to Available, making it ready for sale or dispatch.
• The product will then be included in the active inventory for customer orders and dispatch.
• Inventory Management:
• Products flagged as Not Available will still be visible in the warehouse’s inventory for tracking and reporting purposes, but they will be excluded from inventory that is ready for sale or dispatch.
• The system should support reporting capabilities that allow warehouse staff and management to easily track all products marked as Not Available, so they can manage repair workflows and return these products to active inventory.
• Repair Workflow:
• Products marked as Not Available will trigger a workflow for inspection and potential repair.
• Once repaired, staff can manually update the product’s status to Available, signaling that the product is ready to be restocked for sale or dispatch.

Workflow Overview:

• RMA Process and Return:
• A customer returns a product through the RMA process.
• Upon booking the product back into the warehouse inventory, the system automatically flags the product as Not Available, assuming that the product may require repair or inspection.
• Inventory Management:
• The product is now part of the warehouse’s inventory but marked as Not Available, meaning it cannot be sold or dispatched.
• A report or dashboard will be available for warehouse staff to track all Not Available products, ensuring they are properly handled and processed for repair or inspection.
• Repair and Status Update:
• If the product is found to be in working condition or has been repaired, warehouse staff can manually update the product’s status to Available, making it ready for use, sale, or dispatch.
• The system will now include this product in the available inventory for customer orders and distribution.

Example Scenario:

• A customer returns a defective television through the RMA process.
• When the television is booked back into the warehouse inventory, the system automatically marks it as Not Available, indicating that it cannot be sold or dispatched.
• The warehouse team inspects the television and performs necessary repairs.
• After confirming that the television is now working, the team manually updates its status to Available, and the television is once again part of the active inventory, ready for sale or dispatch.

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.

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.

Can we have a time bounded territories similar to the characteristics? E.g. Resource A mapped to Territory 1 from 01-Jan to 15-Jan and to Territory 2 from 15-Jan to 31-Jan etc. With this RSO or Scheduling Assistant picks up the best possible resources.

It's quite a common ask among the customers and currently customers have to manually move the resources between territories is a painful process when we talking about 1000s of resources working in multiple territories, travelling across the state/country.