cancel
Showing results for 
Search instead for 
Did you mean: 

From Opportunity Lines to Field Service Work Order Products and Services with Flow

Tested on:
Dynamics 365 version 9.1, Field Service solution version 8.x, Unified Interface

A common customer scenario is one where a core Dynamics 365 Customer Engagement Opportunity form is in use for a sales process. “What do we do with our Opportunity form” is a question that arises in almost every Field Service and PSA implementation where D365 CE is already in use. As Field Service and PSA have their own forms due to their own logic and the “Field Service process” and “PSA process”, the Opportunity forms can be a slight headache. If you want to stick to the core CE Opportunity form and you’re sure you have no need for the app specific one, this blog post will introduce you to an idea that allows you to pull products from Opportunity Lines to your Work Order Services and Work Order Products with Flow. No code is needed to accomplish this!

The Flow fires off when an Opportunity is closed as won. Products set on Opportunity Lines will be pulled on the Work Order Product and Work Order Service entities, after a Work Order is created. As Field Service has Inventory, Non-Inventory and Service products, these different options are identified at the Switch Casesection of the Flow, before Work Order Services and Work Order Products are created. For more information about Switch Case, please see this post by Flow’s PM Stephen Siciliano.

flow-opportunity-lines-to-work-order-products-and-services.png

 

Running the Flow

Products are added on Opportunity Lines and the Opportunity is closed as won.

opportunity.png

 

The Flow executes and creates a Work Order, Work Order Services and Work Order Products.

switch-case.png

The Work Order has all the products from the Opportunity Lines on the related WO Service and WO Product entities.

 

services.png

 

products.png

  

As always, this Flow can be found from the Those Dynamics Guys PowerApp Bank here. Huge thanks to both Elaiza Benitez and Kimmo Koski for their help.

Disclaimer:
This posts reflect my personal opinions and findings unless otherwise stated.

Comments

Great Article Annti!

I think you have caught the essence, although I have used a slightly different approach when solving the same issue.

One thing that I have thought about is how to create a Work Order from Flow without changing the requirement level of the Work Order Number from Mandatory to Optional. Does anyone have a sugestion on this, or have solved it in any other way.

Regards,

Joakim

Hi Annti,

 

While creating WO, i got the following error 

{
"status": 400,
"message": "The currency must be the same as the currency on the price list.",
"errors": [],
}
Meet Our Blog Authors
  • Experienced Consultant with a demonstrated history of working in the information technology and services industry. Skilled in Office 365, Azure, SharePoint Online, PowerShell, Nintex, K2, SharePoint Designer workflow automation, PowerApps, Microsoft Flow, PowerShell, Active Directory, Operating Systems, Networking, and JavaScript. Strong consulting professional with a Bachelor of Engineering (B.E.) focused in Information Technology from Mumbai University.
  • Encodian Owner / Founder - Ex Microsoft Consulting Services - Architect / Developer - 20 years in SharePoint - PowerPlatform Fan
  • Cambridge UK Power Platform User Group Leader, Technical evangelist and speaker. Always says yes to coffee! #LetsGetCoffee
  • Passionate #Programmer #SharePoint #SPFx #Office365 #MSFlow | C-sharpCorner MVP | SharePoint StackOverflow, Github, PnP contributor