3

Add a completed y/n flag on the WO Incident

In case of managing multiple incidents on a single WO, the follow-up resource could not track what incidents were solved from the first visit, and what were not due to the following : 1-First visit resource can not complete the WO as only 1 incident has been solved and the work is not done 2-T...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
Declined
Ideas Administrator

Thank you for your feedback. As this may not align to how a significant portion of our customers manage their work, for now, we will not implement this at the product level. Further, if this is important to how this is managed for a specific implementation, it is a simple enough addition to add.

Sincerely,

Jason Cohen

PM, Microsoft.

3

Anomalous Work Order Identification

Use machine learning to highlight Work Orders which are significantly outside of the norm is some way (Price, Duration, Number of bookings, etc.) to allow organizations to look at a select list of work orders which may yield both opportunities for an organization to learn how to improve their ...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
Needs Votes
3

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...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
Declined
Ideas 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)

2

Field service work order integrate with contact

Account selection is mandatory to create work order, all our business cases are work order related to contacts. we sell insurance products, tyre, and batteries directly to our contacts, not accounts.


we can create opportunities, and cases for a contact but I am not able to cre...

Read more...

1 Comments

Read more... 1 Comments

Category: Work order (81)

STATUS DETAILS
New
2

Quick Search Limitation of 10,000 records

Currently, when we are doing the quick search on the work order list if the results are more than 10,000 it throws the error and stops. All of this happens at the backend so on UI side it looks like nothing is happening and the quick search does not bring back any results. It would be great if...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
New
2

Do not update Work Order 'System Status' when the sub-status is changed and System Status is not different

The current system behaviour is that when a Work Order Sub-status is updated on a Work Order, the System Status value is updated even if it is not different to the existing value.


This causes multiple triggers of Processes and Fl...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
New
2

Adding Incident type to work order takes time to copy data

When a work order is created, incident items such as products, services, and service tasks are copied to the order using the "Field Service - Copy Incident Items to Work Order" (LongJobs_CopyIncidentItemsToWorkOrder (number 464)) system job.

The documentation says that the system task is...

Read more...

1 Comments

Read more... 1 Comments

Category: Work order (81)

STATUS DETAILS
New
2

Word Template to use Product Name Language Translations

Word Templates created for Work Orders are used to create documents to send to end users a Work Document.


When this template includes Work Order Products and Work Order Services, these have Product Names included. The Product Names have Translations loaded in the different la...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
New
2

Work order arrival time

The possibility to begin/arrive early in a work order. Right now when you want to change the work order status to "In progress" it's mandatory to select the "Actual arriving time" and it can't begin earlier than the "start time" or later than the "end time", this doesn't allow to track all the...

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
New
2

Log the Auto Number trace to the Plugin Logs

Log the Auto Number trace to the Plugin Logs

Read more...

0 Comments

Read more... 0 Comments

Category: Work order (81)

STATUS DETAILS
New