Power Platform & Dynamics CE

In the world of Dynamics 365 CRM and the Power Platform, plugins are powerful tools that allow you to execute custom business logic during system events. But with great power comes great responsibility — especially when things go wrong. This is where Plugin Trace Logs come in. Whether you're debugging an issue or optimizing performance, Plugin Trace Logs provide deep insights into your plugin’s behavior, execution path, and errors. Let’s dive into how you can harness this often-overlooked feature to your advantage. What Are Plugin Trace Logs? Plugin Trace Logs are diagnostic tools built into Dynamics 365 that allow developers and architects to trace what a plugin is doing when it runs — including: Input and output parameters Execution pipeline stages Exception messages Performance metrics Custom trace messages (via `TracingService`) These logs help isolate issues, validate logic, and fine-tune execution time. How to Enable Plugin Trace Logs To start using Plugin Trace Logs, you’ll ...

 One common frustration when building Canvas Apps over Dataverse is encountering this cryptic error:  “This data type is unsupported for evaluation” This message typically appears when Power Apps cannot process or render a specific Dataverse column type within a control or formula. While it may seem vague, it’s usually tied to specific patterns involving complex column types or runtime data structure mismatches. In this blog, we'll explore common causes, scenarios, and practical fixes from both a developer and architectural standpoint. Root Causes of the Error 1. Polymorphic Lookups Dataverse supports polymorphic relationships (e.g., `Owner`, `Customer`, `Regarding`) that can point to multiple entity types. These lookups can't be directly evaluated in Power Apps unless you cast the reference explicitly. Use: If(     IsType(ThisItem.Customer, Account),     AsType(ThisItem.Customer, Account).Name,     AsType(ThisItem.Customer, Contact).FullName ) 2....

Environment Management isn’t just an admin feature—it’s a strategic enabler for solution architects and developers building on Power Platform. Here's why it plays a vital role for both roles: For Solution Architects 1. Design with Governance in Mind Architects can align app and automation design with environment strategies like Dev/Test/Prod separation, data boundary policies, and compliance zones—ensuring scalability, security, and regulatory alignment from day one. 2. Environment Strategy as Architecture Backbone Environment Management allows architects to define:  Region-specific environments for data residency  Dedicated environments for critical workloads  ALM pipelines with clear environment stages  This supports a robust and modular enterprise architecture. 3. Visibility into the Platform Ecosystem With full visibility and telemetry, architects can understand: How environments are used Where capacity is strained Which apps or flows might need restructuring Thi...

 Imagine having your data not just stored—but intelligently understood, categorized, and responded to—all inside Dataverse. That’s exactly what Prompt Columns bring to the Power Platform: a seamless fusion of structured data and Generative AI. In this post, we’ll dive into what Prompt Columns are, how they work, and how you can use them to supercharge your apps with AI, all without needing to be a data scientist. What Are Prompt Columns in Dataverse? Prompt columns are a brand-new column type in Dataverse that allow you to generate values using AI prompts. Unlike traditional fields that rely on user entry or formulas, prompt columns use AI models to populate values based on your instructions. Key Capabilities: Start with a simple prompt (e.g., “Classify this feedback as positive, negative, or neutral”). Use Copilot to help draft your instructions. Choose from basic to premium AI models or bring in custom Azure AI models. Provide context (i.e., “knowledge”) using other fields in th...

In Microsoft Dataverse, data integrity and uniqueness are critical for building scalable, enterprise-grade apps. While Dataverse ensures every row has a system-generated GUID as its primary key, real-world business scenarios often require natural identifiers like Customer Numbers or Email Addresses to enforce uniqueness. This is where Keys in Dataverse—both primary and alternate—become essential. In this guide, we’ll deep dive into:  What keys are in Dataverse  Technical details for developers  Strategic insights for architects  Real-world use cases  Limitations and best practices What Are Keys in Dataverse? A key in Dataverse defines a column (or set of columns) that enforces uniqueness in a table. This means no two rows can have the same value for the key column(s). There are two types of keys in Dataverse: Primary Key (System-Managed) Every Dataverse table automatically includes a GUID primary key (e.g., `contactid`, `accountid`).  Assigned automatically...