Cycle Count Process
In order to manage inventory a user should be able to complete a stock count process. Allow for randomization and set thresholds to encourage appropriate inventory management.
Prevent PO creation overwriting address fields
Thank you for your feedback.
We released this change. The system should now only populate this value if there is not an existing value present.
Thanks again for your great feedback and our apologies for not updating this Idea more promptly.
Jason Cohen
PM, Dynamics 365 Field Service
Alert for customer when technician reached Site
Hello,
Now days people are working on multiple tasks this impacts technician to wait for customer /right customer contact once he reached site.
In these scenarios , if system triggers alert to customer then he will be ready explain issue or arrange right person to assist te...
Thank you for your feedback. We are not considering the suggestion at this time due to the fact that you can create today a workflow that gets triggered on status change of the bookings. In addition we also allow you to integrate with providers like Glympse, that can provide excellent insights to keep the customer up to date on the technicians ETA. Hope this helps.
Sincerely,
Shloma Baum
PM, Microsoft
Retrieve required work order skills from entities other than incident type (e.g. asset, product, customer)
OOTB the work order skills are populated based on the incident type. However multiple customers have explained situations where they would like to specify required skills also on the account (e.g. entry certificate), customer asset (e.g. for highly-customized assets) or product (instead of bui...
Thanks, Alexander.
I really like this idea and will begin to look into it further; however, if this gets more votes, it will be easier to justify prioritizing this idea.
Thank you for your insight,
Jason Cohen
PM, Dynamics 365 Field Service
[Field Service] Ability to create WO from Quote and Order
In Field Service, B2B Scenarios, it is very much possible that a Technician finds a part needs to be replace and B2B , usually, follows a requisition process for procuring the same which take a standard sales life cycle.
In such scenarios, an opportunity is created and nurtured through Q...
Thank you for your feedback.
Unfortunately, at this time, we are not considering this suggestion.
We currently allow Work Order creation from Opportunities. Further, we allow significant Field Service sales functionality to drive FS sales scenarios. Unfortunately, we see this functionality is under-utilized and don't think it makes sense to invest in these use-cases further for the forseeable future.
It is possible that we will revisit these areas, eventually.
We do think this is a valid scenario and we encourage you to enable this with custom logic to support your and your customers' scenarios.
Thank you,
Jason Cohen
PM, Dynamics 365 Field Service
Schedule Board - Starting a Booking Late
Currently if a resource starts a booking early the Schedule Board reflects the Start and End Time that actually occurred however if a resource starts a booking late the behaviour is different in that the Start Date of the booking is not updated. What I would like to see is the option to have t...
Thanks for your feedback.
We don't think it would be appropriate to implement this suggestion.
As you suggest, if a booking is changed to In Progress, we can reasonably assume that the booking needs to move forward to show the start as the moment the booking was updated to In Progress. A booking cannot be In Progress in the future.
However, the same cannot be reasonably assumed in the reverse. If it is now, 10:00am and a booking was scheduled to start at 9:45am, when a schedule board user marks the booking as In Progress, perhaps they are simply doing it on behalf of the field resource who arrived on time but could not update their booking for whatever reason. In this case, it did start at 9:45am. A booking could have been actually begin before the moment it is being updated on the schedule board. From the schedule board, you can always change the time to the accurate time.
I hope this makes sense. Feel free to raise another idea if you think there are scenarios where this explanation does not make sense. If you do, please provide details.
Thank you,
Jason Cohen
PM, Microsoft
Customer Asset - Historical Records
Customer Assets may change over time. They may be upgraded and become a different product, other field may change, they could move accounts so their external id changes etc. Currently if you look at any Work Order/Incident, it shows you the current asset data. So if you look at an old call and...
Thank you for your feedback.
We are not considering the suggestion at this time:
- We don't believe this is a common ask.
- The concept of Asset history may make sense but the idea that we would preserve the asset state against each work order/work order incident at the time of creation is not something we're currently considering. We're concerned that this would lead to unnecessary data duplication, mobile sync complications, and potentially undermines the value of the relational database upon which the system is built.
- If the asset is replaced with another product, is it the same asset or was one asset retired and replaced? We think different organizations may answer this question differently. If we can offer functionality that will serve the majority case, it may make sense to revisit.
Thank you for sharing your idea. While we don't think we will move forward with this one, we hope you aren't discouraged from raising ideas in the future.
Sincerely,
PM, Jason Cohen
Microsoft.
Natively adding more to the Warehouse
OOTB warehouse is very bare. It would be nice to have a some native subgrids on warehouse showing related inventory & vice versus on the product record showing related warehouses and quantity.
Thank you for your feedback.
Currently this is not in our roadmap; however, we think this is a good idea and a reasonable suggestion. We are tracking it and if we get more feedback and votes, we will consider it in the future.
Sincerely,
Jason Cohen
PM, Microsoft
BUG: Field Service JS library not being added to Opportunity Form Libraries
I deployed Field Service 7.3.0.123 to two v9.0 organisations. In both cases I got a JavaScript error when opening up the main "Opportunity" form, for a new or existing Opportunity.
The reason is as follows:
On the main Opportunity form, FS.Opportunity.Library.Load has been added ...
Thank you for reaching out.
Your suggestion seems to be a product bug.
Please reach out to the relevant support channels as specified in Product support (http://go.microsoft.com/fwlink/?LinkID=616937).
Sincerely,
PM,
Microsoft.
Time Entry early access feature
Time Entry early access feature has inconsistent behavior.I have opted it for two trial organizations.On one it is showing Time entry tab but When I tried to create Time Entry it was throwing business process error saying "Date is not specified for the time entry". On another organization,the ...
Thank you for reaching out.
Your suggestion seems like it may be a product bug.
We'd love to take a look to see what may be causing this behavior. Please reach out to the relevant support channels as specified in Product support (http://go.microsoft.com/fwlink/?LinkID=616937).
Sincerely,
Jason Cohen
PM, Dynamics 365 Field Service
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,
Shloma Baum
PM, Microsoft