If you've worked with Dynamics 365 long enough, you know that some error messages are helpful. And some are...well...not quite as helpful. Today’s Problem Yesterday, I was working on a custom Dynamics 365 CRM app when I was greeted with the below upon log in: "An error has occurred. Please try again. If the problem persists, contact your system administrator." I could not load any table (custom or system). What an ironic error message since I am the sys admin! The app existed

You got the Dynamics 365 project. The requirements are clear. More or less. In modern enterprise solutions, it is quite common to have a rich data model with a lot of different tables entwined with each other in various ways. Which naturally creates lookups in forms. This creates connections between records giving the opportunity for a 360-degree view of your customers, leads, opportunities, projects etc. Or in my geeky case of the Avenge 365 app based on Dynamics 365 Sales,

In the last blog post, I covered how Copilot Studio really accesses Dataverse through various lenses with the Dataverse Knowledge Source, Dataverse Connector and Dataverse MCP Server. From the way the core model works, to the way inputs and outputs are managed, schema awareness, CRUD support and bound/ unbound actions. Here is what the summary looked like: Capability Knowledge Source Connector MCP Server Core Model Search/ index based, for retrieval + grounding Deterministic