Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
In this post I am going to discuss creating a work order in Field One Sky for Microsoft Dynamics CRM.
There are actually five ways to create a work order;
In this post I will cover the detail around manually creating a work order, I will mention the other methods in future posts.
Manually Creating a Work Order
You and create (or maintain) a work order directly in the FieldOne Sky options within Microsoft Dynamics CRM, typically this might be done for creating ad-hoc work orders.
Having selected the work orders option click new to create the work order, the process is pretty straight forward. Although there are quite a few fields but you’ll find many will be defaulted from customer preferences or because particular incident types have been recorded. I will attempt to cover all of the various fields and the logic behind each one but there are quite a few so I apologise if I miss the odd point!
Tip: If you are new to FieldOne, don’t dive straight into creating work orders. You’ll need to create resources, service types, incident types (etc) first. Your initial set-up will probably take some time / effort. But once completed creating work orders becomes a simple task.
The work order summary looks like this, below I will try to cover all of the fields and explain their purpose ….
Tip: The scheduled time window could be larger (or smaller) than the estimated time to bill.
Generally speaking, each work order will relate to one incident (the primary incident) but it is worth understanding that you can add multiple incidents to a work order. The services, service tasks and products shown on the work order then become a combination of all the details from all of the incidents added to the work order.
Work Order Settings
Having entered the work order summary, you’ll next scroll down to the work order settings
Note: I assume this field is aimed at situations when a work order might be completed at the depot or out in the field. Something that might be useful in some circumstances. I have however found no functionality associated with this field out of the box. Although you could create a view of all work orders set to “depot” and manually schedule those differently
Time to promised
Date Window start
Date window end
Time window start
Time window end
This note is automatically transferred to the instructions on the follow-up work order.
Work Order Address / Location
The address and location on a work order are significant due to the nature of field work. It is important to check the correct address is recorded. By default, this will be the address of the service account. If the map location is wrong, or the latitude / longitude fields are blank, use the geocode button in the ribbon bar to manually reset these.
Service Tasks, Products and Services
Service tasks, products and services can all be manually added to work orders, although it will be most common that these will be set by virtue of adding incident types. Even if you have used incident typoes to initially ste the values for these you may wish to review and amend these details.
Business Applications communities