For the first time in the series about Microsoft exam PL-400, we’re going to look at our first code related topic - writing client-side scripts using JavaScript. This underpins the importance of leveraging functional solutions, wherever possible, to ensure you build out the most effective Power Platform solution.
As well as having a good awareness of Power Automate flows, Power Platform developers also need to grasp two additional automation tools - Business Process Flows and Business Rules. As we continue my PL-400 exam series, let's dive in to see what these tools can offer us.
As we close out my blog series on exam MB-400, I thought it might be useful to compile all previous posts together into a single location. So if you've been following along or are joining for the first time, I hope this post is useful.
We are back once again with my MB-400 revision notes series! In this post, we round off our discussions relating to user interfaces by discussing command buttons and how to work with them via the Ribbon Workbench.
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…
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…
For an exam like MB-400, which targets developers building code-heavy solutions targeting Dynamics 365 or the Power Platform, you'd expect Microsoft to skip a topic like Business Rules entirely. However, they are very much a feature you should use and fully understand.
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.
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...
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.
Recent Comments