-
This post discusses the importance of sending requests to Dataverse in parallel during integration and migration projects. It highlights the advantages of parallelism, such as reduced processing time and optimal server capacity usage. The author provides coding approaches for both modern .NET and .NET Framework, while stressing key connection settings and constraints concerning plugins.
-
This post discusses leveraging Python with Dataverse, highlighting its advantages for analytics, reporting, and automation in Dynamics 365. It presents a real-world example of a C-level dashboard generated from Dataverse data, showcasing how to efficiently aggregate data, create custom visualisations, and send notifications using Python scripting and the PowerPlatform-DataverseClient-Python SDK.
-
I developed a Dynamics 365 MCP Server for an agentic engineering project, aimed at integrating AI agents with Dynamics 365 operations. Key focus areas included server design, tool registration, and validation of workflows. This MCP framework enhances consistency and supports robust workflows for enterprise applications. Resources for building your own are provided.
-
This post explains elastic tables in Dataverse, highlighting their structure, creation process, and key considerations. Unlike standard tables, elastic tables, backed by Azure Cosmos DB, support high volumes of semi-structured data and automatic scaling. They are ideal for unstructured data but lack transactional integrity typical of relational databases.
-
Alternate keys in Dataverse can significantly simplify integration projects by serving as unique identifiers that bypass the need for GUID lookups, thus reducing API calls and potential errors. They allow efficient syncing between systems by enabling operations like retrieve, update, and upsert directly through natural business keys, enhancing overall performance in data management.
-
The post highlights the challenges of tech sprawl in Dynamics 365 projects, where business logic gets fragmented across multiple tools, complicating debugging and maintenance. It advocates for a streamlined architecture using one technology per concern, emphasising plugins for server-side logic, TypeScript web resources for UI, and Power Automate for approvals, to enhance governance and manageability.