Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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
It appears to me that the standard Field Service product is designed to work in B2B scenarios only.
Still, it could very well be possible that work orders are not created in scope of an account but rather in the scope of a contact.
Have you ever come across such requirement?
If so, how did you overcome it?
I know that the standard solution is quite sensible it comes to extensions.
Hence I’m curious if someone else has already successfully extend the standard for such a scenario.
In many cases I have seen people create dummy accounts for a contact or even use the account as an equivalent for a household with multiple people in it. Btw, this is similar in other CRM solutions, e.g. Siebel's CPQ capabilities were centered around accounts as well. Didn't stop implementations from managing millions of B2C customers, so conceptually this should be okay.
Yes, it can be done for B2C. In many cases, Accounts in a B2C scenario are "Households". The Contacts are the people within that household. If you want to keep it as close to OOB as possible, this would be a way to do it.
Business Applications communities