Power Apps Component Framework (PCF) controls are a new, shiny, thing that Power Platform / Dynamics 365 developers can work with. They are also a subject area within Microsoft exam MB-400. Therefore, in my next post on my series targeting this exam, let’s see how they work.
It's taken seven posts into my MB-400 developer's exam series for us to start talking about our first code related topic, client-side scripting using JavaScript or TypeScript. And, as we'll see, this is something you should only really resort to after thoroughly exhausting the capabilities within Business Rules…
DevOps and Dynamics 365/the Common Data Service can go together like peaches and cream, with a bit of effort and utilisation of some community tools. And, as always, you may end up having to contend with pesky errors, such as one I had recently involving a TimeoutException...
Dynamics 365 and Power Platform developers should always use Business Rules over JavaScript / TypeScript form functions. Full stop. However, there are situations where the native capabilities within Business Rules are not up to scratch, such as when you start working with multi-select option set fields…
OAuth authentication, especially involving the Common Data Service or Dynamics 365, is a subject you may not grasp fully the first time around. The technical setup required can be tricky to understand or even implement at all, meaning you find yourself dealing with error codes such as AADSTS65001.
Developers typically get the short end of the stick in lots of things, and consistent learning tools is one area I’d highlight, particularly in the Dynamics 365 space. Fortunately, this no longer appears to be the case, thanks to the release of exam MB-400.
Custom pricing is an invaluable feature within Dynamics 365 Customer Engagement, that can be used to fine-tune your sales processes. If you're interested in finding out more about them, then my latest tutorial video is for you - find out more in this post!
Project Service Automation (PSA) can be a beast when first approached. The application contains a breadth of functionality which is not always properly documented and can be challenging to figure out. To find proof of this assertion, we only need to look at how price list mark-ups and discounts operate.
It seems to be non-stop changes and announcements when it comes to licensing for Dynamics 365 Customer Engagement at the moment. Now, as we move into September, we get yet another, which informs us of some potentially troublesome API limits, that will take effect from October onwards.
Having the ability to straightforwardly obtain a records Globally Unique Identifier after programmatically creating it within Dynamics 365 Customer Engagement can help significantly with data integration requirements. This is a relatively easy task when working with the Web API using JScript but less so if C# is your language of choice...