Search for a command to run...
Series
Unit testing Dynamics CRM plugins can become tedious when you rely on fully manual mocks. Each dependency, the organization service, plugin context, tracing, must be simulated by hand, and even the smallest mistake leads to hours of debugging. This i...
When building plugins for Dynamics 365 CRM, developers often start with Late Bound entities. It’s a flexible approach, but flexibility isn’t always your friend. As your project grows, Late Bound code becomes a jungle of string literals, manual consta...
After building the “Contact Associate” plugin and confirming that the FetchXML logic works, the final development step is validating the behavior through manual unit testing. This approach allows you to test the plugin locally, without depending on e...
In the earlier phase of this build, we focused on extracting the email domain from a new contact. Now we take the next step: using that domain to automatically identify and link the contact to the correct account. This level of automation adds intell...
When integrating external systems with Dynamics 365, it’s common for new contact records to be created without an associated account. This gap can disrupt hierarchy, reporting, and business processes. A practical and elegant solution is to automatica...
In Dynamics CRM and Model-Driven App development, working with data is at the heart of everything. In earlier steps, we focused on processing data that already exists inside a plugin’s Target entity. However, real-world plugins often need to retrieve...
