I have recently published an article on MS Dynamics World discussion the rise of Dynamics 365 and the Power Platform in the Real Estate, Property and Housing Market. I also discuss the reasons for this and why other old-time established vendors are unable to compete. Keen to hear everyone views on this (no swearing!).
The post is inspired by our own firm’s experience (TechLabs London) in the Dynamics 365 platform and in the Property and Housing Industry through our solution (iProperty Cloud)
Here is a link to the article – feel free to comment below or on the article itself:
If you read my previous post, Introduction to PCF: The Future is NOW! you will know that I am extremely passionate about PCF. However, this passion is not just because this is the direction Microsoft Power Platform, PowerApps and all Dynamics 365 1st Apps are going. It is a passion because I do believe it has filled a gap we always felt when building Dynamics 365 CRM solutions for many years. This gap was the lack of ability of building native components within a Dynamics 365 Form, View and Dashboard. Many years ago, we did IFrames (yeah – sounds bad but was normal then) and then we used Web Resources all the way. Now, it is PCF!
So, you want to learn more about PCF, here are some really interesting resources to get you going (updated regularly):
Microsoft PCF Resources:
The Infamous PCF Gallery: https://pcf.gallery/
Official Documentation: https://docs.microsoft.com/en-us/powerapps/developer/component-framework/overview
PCF Tooling: https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf
Introduction to PCF: https://www.youtube.com/watch?v=WNDbZcgVMi0
PCF Forum: https://powerusers.microsoft.com/t5/PowerApps-Component-Framework/bd-p/pa_component_framework
Microsoft PowerApps Component Framework, widely known as PCF, is framework that allows PowerApps Makers and Dynamics 365 Developers build code components for model-driven and for canvas apps (currently public preview) to provide enhanced user experience for users to work with data on forms, views, and dashboards.
In other words, PCF is framework that can allow you to build any control to embed natively on any Model-driven form (and now canvas apps).
For example, a field that displays an integer value, can be replaced with a custom PCF control in the form of a colourful slider or a dial or a knob or whatever your imagination take you.
Many are asking how different is Dynamics 365 and PowerApps PCF from Web Resources that we have spent years using to build custom embedded screens. PCF is different. HTML Web Resources are rendered separate to the form, while PCF is rendered as part of the same context and loads at the same time as any other native component on any Dynamics 365 / PowerApps form. Most of Microsoft’s modern components and 1st Apps are built based on PCF. For example: Most of Dynamics 365 Marketing custom controls are build as PCF components and re-used throughout the Marketing solution.
You can read more about PCF in Microsoft’s official documentaiton:
The Future is Now!
When you think about PCF, don’t think of it as this future way of building components. While you can still build HTML Web Resources, PCF is the new norm and you better get used to it! Here at TechLabs London, we have re-built all of our custom components as PCF for both our IP add-ons and throughout our iProperty Cloud solution modules.
So, if there is anything you can take away from this Post, please make sure it is:
Starting building your custom components in PCF now and don’t wait until it becomes more widely used. It is the future, but we have it now!
This is something I have tried for quite sometime now under NDA and a Private Preview programme which I found to be really interesting and powerful. This is the ability to embed an existing Canvas App to show up inside model-driven forms. This is now available and really opens up a lot of opportunities for creating pixel-perfect canvas apps that can then be embedded inside Dynamics 365. For example, you can have your Canvas App that reads data from SharePoint, embedded inside your contact entity form. How cool is that!
This is now Generally available. Here is the official announcement:
What is the difference between Microsoft Dynamics 365 and PowerApps? Are they the same thing? Is PowerApps different form Dynamics 365 CRM? What is common between PowerApps and Dynamics CRM or Dynamics 365 Customer Engagement?
I did a webinar on the 10th Mary 2019 where I tried to answer all these questions and I have also covered few more related points. Watch the video here or on my YouTube Channel