ENGINEERED CODE BLOG

In order to confirm that much of the functionality in Dynamics 365 Portals works with virtual entities, I needed to have data sources with some pretty specific fields. Rather than hunting for an existing service to meet all of my requirements, I was able to quickly setup a fake OData service hosted in Azure Web Apps that I could use as my Dynamics 365 Virtual Entity Data Source.

So far in this series I’ve provided an intro on virtual entities and a deeper dive into virtual entities and relationships. In this post, I’m finally going to talk about how they work with Microsoft Dynamics 365 Portals.

In my first post in this series I discussed how virtual entities and the link-entity node in FetchXML don’t mix well. In this post I’m diving a little bit more into virtual entities and how they can be related with other virtual entities, as well as non-virtual entities.

One of the great new features available in Dynamics 365 v9 is Virtual Entities, which allow you to represent data from external system as entities without copying or synchronizing data, and often times without any custom code. In this series of posts, I’ll dive into this new feature, with a focus on what it means for Dynamics 365 Portals, and how we can leverage them to create no-code integrations between your Dynamics 365 Portal and other systems.