In my last post I looked at how some of the core Sales entities are read-only in everything except their default state, and how you may need to go through a series of transitions between different states to edit them. Although these are the only entities I’m aware of that Continue Reading
If you work with the standard D365 Sales entities like Quote, Order and Invoice you might have had users come across error messages like Most entity types have Active and Inactive states but can actually be edited via the API even when they’re inactive. These three sales entities have some Continue Reading
I’ve written a fair few apps to integrate with Microsoft Dynamics 365 over the years, and you can guarantee at some point you’re going to hit an error that’s triggered by a plugin when you update a record. How do you find the true cause of the error and start Continue Reading
I’ve recently been looking at a few cases where I’ve got seemingly incorrect results from my FetchXML queries. This can manifest itself as the results limited to 50,000 records or records being skipped. I’ve narrowed these down to some behaviour I wasn’t aware of when you retrieve multiple pages of Continue Reading
Matt Beard & I spent some time investigating the new asynchronous merging functionality today and how it impacts Data8 Duplicare (it doesn’t, Duplicare continues to work as normal). If you haven’t seen this already, when you merge two records you’ll now see the message: The selected records will be merged Continue Reading
Disclaimer: the details in this post are based on the best guesses I’ve been able to make about how this works, which are derived from the behaviour I’ve seen while using it. I don’t have any official information on any of this, so use at your own risk!
The ability to merge records is a powerful one in keeping control of your data quality within PowerApps / D365. It can also be deceptively complex. As we’ve been living & breathing this area of the platform for several years during the development of data8 duplicare, we’ve seen a lot Continue Reading
If you’ve been working with plugins in Microsoft Dynamics 365 for a while, you’ve probably come across the IExecutionContext.Depth property. This tells your plugin how deep in a call stack of plugins it is. A depth of 1 means it is being triggered by a direct user action, e.g. updating Continue Reading
One thing I love digging into with Microsoft Dynamics 365 is all the “special” actions. Although just about any entity type can be used with Create, Update, Retrieve etc., there are a lot of other actions that do more specialised jobs, and QualifyLead is a great one of these.