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 ...
Add option to Work Order Type to get Price List from Service or Billing Account
Currently, the work order inherits the Price List value from the Work Order Type assigned. Often, the price list is actually a property of the Service or Billing Account. Recommend adding an option set field to the Work Order Type called "Price List Source" with values 'Work Order Type', 'Bill...
Thank you for your feedback.
We are not considering the suggestion at this time, however, that is because it is already possible to satisfy this with OOTB behavior. Using entitlements, you can drive pricelist application through many different configurations. It will not apply at the WO level, but will apply at the specific WO Product or WO Service levels. It will even allow variable application with different pricelists applying to different WO lines based on their unique applications.
We sincerely hope you'll look into this existing feature as we believe it will allow this capability and much more complex scenarios.
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
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 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.
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...
Dynamics 365 Field service privacy field instructions
Wish we future feature the option to include privacy field instructions in the event to prevent potential inconveniences to the customer-consumer (e.g. construction site, vehicle pick up/drop off, time or schedule of customer, respecting lunch and birthday dates or times, etc...).
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...
Creating Incident Type from a work order
Currently, avenues for incident types are as below. 1. Creating incident type from model-driven app 2. Uploading incident types through importing 3. improving Incident type through AI suggestions While creating a work order for which no specific Incident type is available (consider a situation...
Administrator
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