Microsoft Dynamics 365
How can we improve Dynamics 365 ?
Suggest a new Idea
Search for existing ideas
Usage Based Maintenance Schedule
So many of our customers repair products based on hours of usage. replace belts at 300 hours, inspect something at 200 hours. We should have the ability to build maint schedules under products or assets which then automatically generate work orders or work order tasks when these Timers are met...
Thank you for your feedback. We think this idea has merit.
We need some more details to understand this suggestion better:
Obviously, we would want such a feature to be useful and not another manual task. We're eager to see what kind of votes this gets.
PM, Jason Cohen
Allow to have differing Incident pattern within a Agreement Booking Setup
Or Field Service customers often ask how to set something like this up: Incident Type A monthly Additionally Inc Type B every quarter Additionally Inc Type C every year So that a yearly maintenance job consists of Inc Type A,B and C but a monthly job contains only A. Another example: If you ha...
Thank you for your feedback. We love this idea.
Interestingly, this is something we've been discussing as part of our roadmap; however, we do not currently have concrete plans to implement it. Anything you can do to get this idea more votes will help us increase the priority of this feature in future planning discussions.
Thanks for sharing, Jason Cohen PM - Dynamics 365 Field Service
Set a start and end date for invoicing Agreement invoice products
It would be great that we can provide a start and end date to agreement invoice products so you can make the transaction to:
Start invoicing a new product starting on 1st of april, creating the agreement invoiceproduct on the 5th of january for example.
We need it to be in the same agreement inv...
Create Agreement Templates for Rapid Agreement creation
We have many clients that have recurring work that is high-volume, low-complexity. As such, setting up the work needs to be as rapid as possible, and making an agreement from scratch is painfully slow and prone to error, even when coming from the quoting process.
Having an agreement template th...
Thanks, Wayne, and sorry for the slow response on this.
I think this is a great idea which we've seen implemented in various ways successfully for different customers. That said, we know we need to do more to make the Agreement creation process easier and more usable and we welcome your feedback.
As for a specific agreement template process, we'd like to give this more time to see how the community responds to this concept.
In the meantime, one way this can be nearly acheived using largely out-of-the-box functionality is through the "Agreement Copy" functionality which allows you to copy an Agreement (and Agreement sub-records).
Thanks for raising this,Jason CohenPM, Dynamics 365 Field Service
Booking creation by agreements to respect resources unavailable time
When an agreement is creating recurring bookings, typically to a prefferred resource, it is not respecting if that resource is unavailable. A booking may be in conflict with the resources work-schedule, workday breaks, approved time-off requests, planned abscence / sick-leave or that a resourc...
Thank you for your feedback.
We think of the auto-booking creation by the Agreement Booking Setup record like a recurring meeting in Outlook. If a recurring meeting is created, Outlook doesn't try to move the booking to another person or time if the attendee is busy, on vacation, or in another meeting, it will simply create the booking at the time and for the resource specified.
If you consider what moving the booking would mean, even if we wanted to move the booking more intelligently to another resource or time, how should we universally move the booking to a spot that the business will find suitable? The solution quickly begins to look a lot like the Resource Schedule Optimization add-in. Which is ultimately what we'd suggest for more responsive, intelligent booking scenarios. The system would book unscheduled work orders or would move the recurring booking to a new resource or time depending on the configuration of the RSO.
As always, we really appreciate your feedback. Keep the suggestions coming.
Thank you, Jason Cohen PM, Microsoft
Monitoring and Alerting when record auto-generation fails in agreements
I think the system should alert a user when an agreement fails to generate an invoice, work order or booking as configured by recurrence. It would also be useful to be able to report on what records are expected to be auto-generated to compare with actual records auto-generated.
Allow Modification to Agreement Booking Dates
Allow for the ability to change an agreement booking date to processed and update the associated details. This would allow for the scenarios where a technician is onsite and also completes a maintenance or sells a maintenance agreement and completes the first service for that agreement. Currently...
Thanks for raising an idea.
We think the spirit of this concept is already possible. While you cannot manually update an Agreement Booking Date to "Processed" you can manually update it to "Cancelled," which seems like what has happened in the scenario you've proposed. The Agreement Booking Date is only intended to be "Processed" when a Work Order has been generated from that date.
If this is a traceability question and one of your customers has a scenario where they are conducting a future maintenance which they are aware of through other means (since the maintenance has not yet been generated) and want to be able to trace this against the Agreement, at this time, this doesn't seem like a sufficiently common use case that we should adjust the product to support it. That said, we can envision the scenario where this could occur and, for customers where this makes sense, we think a custom field to trace the related work order added to the booking date or some other customer-specific extension seems like a very viable way to meet a somewhat uncommon use-case.
If you think we've missed some key aspect of the scenario, we encourage you to raise another idea to clarify our understanding.
Thanks,Jason CohenPM, Dynamics 365 Field Service
Agreements - Enable Booking Recurrence to be importable through an Import CSV
Currently, if/when you need to migrate Agreements data (or create a sales demo that involves Agreements), there is no way to import Recurrence. Would be great to be able to be able to define and import recurrence patterns so that we don't have to set it up manually on each Booking or Invoice Setu...
This is technically possible, today. If you'd like for all of the recurrence dialog's fields to be on the Agreement Booking/Invoice Setup forms or if we want to store these recurrence values as a related entity that can be associated to the ABS/AIS, these are ideas that we could discuss further.
For those not aware of how this can be accomplished, today, I'll share a few things that will help, below:
- The recurrence dialog, when saved, populates a field on the ABS/AIS records.- The field is called Recurrence Settings and, by default, it is not displayed on the form.- If you want to import ABS/AIS records through CSV, just get a representative string from an ABS/AIS that is set up similarly to how you would like the imported records to be configured.- With that string, you will see that there are some values driving how the record behaves that can be parsed out of that string, like start and end date, monthsevery, etc.- Use these sample strings to populate the Agreement Booking and Invoice Setup records into a spreadsheet and use this to import fully configured records.
I hope that helps but feel free to reach out if you have additional questions.
Agreement - Calculating estimated cost based on Agreement Booking Setup + Agreement Invoice Setup
Requirement: Ability to capture the customer’s Budget and compare against the estimated agreement cost derived from the information specified on the Agreement, so that users have the necessary information to support the decision making process prior to finalising the agreement. E.g. if t...
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