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.
When you use the RetrieveMultiple method to query data from D365 CE, it’s easy to take the results and assume that’s everything, especially when you’re working with small test data sets.
MSDyn365 MVP Jonas Rapp threw down a challenge on Twitter last week: True, I’ve been ignoring for too long…If you know some C# and some #MSDyn365 WebAPI queries – please help…! 😊Pull Requests accepted! https://t.co/7iHp6XzQbf — Jonas Rapp ᴹᴠᴾ 🇸🇪 (@rappen) March 4, 2019
If you’re a Microsoft Dynamics 365 (hereafter called CRM, because I’m too old to change) admin or developer, you’ve probably used XrmToolBox. If not, go and check it out now. I’ll wait.
As I wrote about recently, I’ve started using Azure Batch to run OpenAPS Autotune jobs for AutotuneWeb. The other day however, I started a job of my own and got a notification that my job was 48th in the queue. Either the service has suddenly got really popular, or something’s gone wrong.
The AutotuneWeb system described in Part 1 is made up of 4 services in Microsoft Azure working together as illustrated below:
Three years ago our first son was diagnosed with Type 1 Diabetes (T1D). Over the next few months we quickly got used to the process of calculating the amount of insulin required for meals and high blood sugar, and adjusting those calculations on a trial-and-error basis. As a software developer I felt sure there should […]