There are numerous tutorials for creating an OData API in .NET, but we’ll be focusing on how to ensure your OData API integrates with Dynamics with minimal headaches. The current dearth of VE documentation can be frustrating, so we did some homework to make your life easier. Here are our 4 main discoveries, shared to help you avoid shooting yourself in the foot.
If you were excited about the release of Virtual Entities as part of Microsoft Dynamics 365, you were probably equally puzzled about the limited documentation available. There is virtually (pun intended) no information on integrating Virtual Entities (VE) into a production environment. Many examples online don’t go beyond a “Hello World” integration using the Purdue course API. Fortunately, we have investigated Virtual Entities for a few of our clients and wanted to share our discoveries as to the limitations and benefits.
In keynotes and sessions at Microsoft Ignite 2018, many stories of organizations that are leveraging Dynamics 365 to fundamentally transform the organization to meet the changing expectations of customers were shared. These success stories are compelling, however it begs the question: “what’s the true return on investment (ROI) for an average Dynamics 365 deployment?” Thanks to an independent analysis from Nucleus Research, we can reveal the answer: