PCF controls are no longer new and shiny, but they remain a powerful tool at the disposal of Power Platform developers. And, much like MB-400, they remain a crucial topic within the PL-400 exam and the focus for today’s blog post.
Microsoft Ignite 2020 took place earlier this week, and there were oodles of new capabilities announced to make any Microsoft 365, Azure or Power Platform enthusiast happy. With this in mind, let's take a look at my top five announcements from the event.
We're back once more with another post in my MB-400 revision note series! And, this time around, we dive into the many capabilities that plug-ins can deliver for developers after tools such as Power Automate or Business Rules have been fully exhausted.
Having never used the feature before, I recently discovered the benefits of the Schema Comparison tool within SQL Server Data Tools. By using this, it allowed me to resolve a baffling issue involving a database project and a computed column field...
Recently, I've been ducking and diving into some deeply technical areas involving C# which, while interesting, has had its share of struggles and lessons. One such experience I'd like to share consists of the use of Entity Framework Core when working with views from SQL Server...
It's relatively rare that you will find differences between what's available in Power Automate flows and Logic Apps. The Common Data Service is perhaps the exception to this rule, as its missing some options to allow you to define which attribute data to return from your instance...
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.
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…
Keeping things simple is an idea I like to promote at all times, particularly in the world of IT. Adopting this mantra can lead to fewer headaches and, as a recent example involving Azure Template deployments within Visual Studio demonstrates, a much faster resolution to your particular problem.
Migrating across from Microsoft Flow to Azure Logic Apps is ridiculously easy. However, there are some critical feature differences that you must make yourself aware of. One difference relates to how triggers actions work, particularly in tandem with an Azure template.
Recent Comments