In last week's post in my MB-400 exam series, we saw how you can use model-driven apps to build data-driven applications. The other type of Power Apps - canvas apps - throws this approach completely on its head, by providing a wholly tailorable visual and data access experience.
It's week 3 in my series all about Microsoft Exam MB-400 and, this time around, we take a deep dive look into the various components that make up a model-driven Power App – with another instructional video to help you along.
It's the second week of my series focused on Microsoft Exam MB-400 and, in this weeks post, we're going to dive into some of the core, functional customisation topics within Power Apps and Dynamics 365 that you must have a good awareness of before tackling the exam.
Having sat the new exam for Dynamics 365 and the Power Platform now's as good a time as any to do another series providing revision notes for MB-400. In the first post, we dive deep into the theory behind creating a technical design involving the Power Platform.
Have you looked at the Power Apps Component Framework yet? If not, you’re missing out on an exciting way to extend Dynamics 365 or model-driven apps in unique ways. Just be sure to pay close attention to your data types, particularly when working with the systems Web API…
IT enterprise projects, particularly ones involving the public cloud, can often be a nightmare from a corporate governance perspective. Fortunately, if Microsoft is your chosen vendor, you can get access to a website with tonnes of useful assets to help you sleep a little more easily.
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...
By default, the Dynamics 365 Customer Engagement connector for Azure Data Factory V2 exposes a predefined list of fields, that must have data mapped to them for any Copy Data task to complete successfully. This behaviour can be impractical depending on your particular scenario; fortunately, there is a way in which you can override this.
Feature deprecations can often cause some degree of disruption, especially if they involve custom code. Microsoft has recently deprecated the Xrm.Page object for JScript form functions in Dynamics 365 Customer Engagement. Find out more about this change and what you will need to do to fix this as part of this week's blog post.
Azure Data Factory V2 not just has 1, but three separate connectors that all claim to hook up to Dynamics 365 Customer Engagement/Dynamics CRM! So which connector is the "right" one to use and what differences do they have? With a little help from Alan Partridge, we can clear up any confusion...