Dynamics 365 Customer Engagement, CRM, Microsoft CRM, Dynamics CRM
This weekend I was so fortunate to talk at the Field Service BootCamp. I have tried to design the Field Service solution to be as simple as possible. I remove most of the logic from view, but keep the essence of the process. What do you think?
Check out the recording from my session here:
Honestly I can’t remember what year Microsoft implementet separate Account & Contact fields for Opportunity, but it has been a while.
Neil Parkhurst describes the issue in his blog from 2015
So why am I fussing about it now? Well, after all these years Microsoft is still using the Potential Customer field for Field Service.
Did you ever see this message in Field Service?
As you can see from the image above, the Potential Customer has been set to a Contact.
Standard behaviour is that Account should overwrite the contact, and therefore always show account if account is present. Sometimes this doesn’t happen, and then you will receive the following error when trying to convert to Work Order.
The fix is extremely simple. Dear Microsoft, please just read from the Account field😊
If you for some reason feel the same about this, I created a suggestion for improvement..
https://experience.dynamics.com/ideas/idea/?ideaid=0d39cacc-562d-ea11-8454-0003ff68a4d6
CRM Keeper 