On change of Primary Incident Type also replace subordinated records
After a new Work Order is created and a Primary Incident Type populated, at least the following records get populated into the new Work Order coming from the Primary Incident: - Work Order Products - Work Order Services - Work Order Service Tasks - Characteristics If a User changes the Primary...
Dynamics 365 Field service warranty tracking and ledger posting
Wish we future feature the option to easily track warranties along with warranty ledger posting, warranty retrieval and easy warranty accrual and warranty deferrals after warranty may had expired.
Utilize booking time stamps to create work order services
Allow for an association between booking time stamps and work order products (could also associate by incident type). Generate work order services when the booking time stamp is created or have a flag to determine timing to generate. In many implementations clients are not understanding the dis...
Add relationship between Work Order Service Task and Incident Type Service Task
When the Work Order Service Task is generated from Incident Type (OOB logic), the ‘Name’ field (on Work Order Service Task) is populated with Service Task name (Task Type Name) I think in many scenarios it would be better to use Incident Type Service Task name instead. It would be ...
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Jason Cohen
PM, Dynamics 365 Field Service
WorkOrder not refreshed after resource booking
Not to be refreshed Work Order Form once a Resource_Booking is created via "Book" button and clicked Book&Exit. The page remain unchanged, and requires MANUAL Work Order refresh action STEPS: Go to Case Create WOrkOrder Click "Book" Select Resource Click "Book&Exit" ISSUE: the Main Wor...
Thank you for your feedback.
I really like this idea. I'm going to look into whether this is possible and, if so, how much work it would require and whether there are any complexities to consider around refreshing the form. That said, currently this is not in our roadmap; however, we are tracking it and may consider it in the future.
Sincerely,
Jason Cohen
PM, Microsoft
Category (Role) as part of Work Order Item
My client would like the role to be selectable, same as , characteristic when when creating 'work order item'. This can be peformed currently by plugins. Most of my clients prefer vanilla systems. Is there a reason why does the category (Role) does not also appear as part of the Work Order Item...
Support for Re-visits
It is very common that a second visit is required when the job can't be completed. Reasons can be that a part needs ordering, the customer is absent or the engineer gets diverted mid travel or work to a more urgent issue. One way of handling this is to use a booking status with FS Status of cance...
Dynamics 365 Field Service option to integrate with legal entity fixed assets
Future featuring option to integrate with legal entity fixed assets records (e.g. Maquiladora) maybe optimum, in addition to supply chain or asset management customers. Not featuring integration with legal entity fixed assets, user may potentially not easily track and document fixed asset or fix...
Dynamics 365 Field service referral commission functionality
Wish we future feature the option to potentially track referral commission functionality based on 3rd party contact person and/or future potentially download from social or professional platform network. Not featuring referral commissions functionality, user may potentially process network commi...
Dynamics 365 Field Service scheduling distribution from resourced pools
Wish there is the option to future easily process scheduling distribution based on fixed resources (technicians) pools. or process a reverse scheduling instead or in addition to the conventional scheduling on a day by day, month or quarter or annual basis. For purpose to easily calculate schedul...
Administrator
Thank you for your feedback.
Since we support the concept of multiple Work Order Incidents per Work Order, this would likely cause some additional complexity. While it is not our expected scenario, it is possible that there are customers that use the Primary Incident field to apply multiple incident types. For those customers this would be a breaking change.
As this doesn't seem to be an overwhelming need, this would cause an unpredictable change for existing customers that have come to understand how it currently works, and that a customer that wants it to work in this way could consider adding additional validations to make the system operate in this way, we won't plan to make this change at the product level.
However, we welcome your thoughts on ways the system should be improved and we hope you will keep providing additional suggestions in the future.
-Jason Cohen
(Microsoft PM)