Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Field Service updates!Learn about the key capabilities and features of Dynamics 365 Field Service and experience some of the new features.
Download overview guide | Watch Field Service video
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 | Upcoming TechTalks
I am a bit confused with the sales cycle with field services.
Yes I am just doing the trial now so hoping I missed something obvious.
I am used to PSA when we started with a Opportunity, then quote and then a sale order was created. At this time we created a project and invoiced accordingly.
So with FieldServices, how would this cycle work?
If I can only create a work order to schedule from a quote or an agreement (as I understand it).
This does not make sense.
My logic would be to opportunity-quote-salesorder-invoice -workorder.
I sell the service, invoice for it then create a work order to schedule a technician to do the install.
What am I missing?
There are multiple sources from which you can create work orders. We often see direct creation from an IoT alert or the portal or an ERP system, conversion from case or opportunity, or the creation from agreements. The problem that I would see with quotes, orders and invoices is that this often happens outside of Dynamics. The opportunity is really the smallest denominator and it has customer details and products/services, so you have all you need to create a WO. However there shouldn't be anything that prevents you from creating a WO from any other entity.
Business Applications communities