![]() ![]() The api used to get your image does not return a resource. However images you want to include to your component will not load. This work great for actually testing your logic. You can debug the component on your local machine where you can test your component. Just so you know what happens behind the scenes. I recommend checking that out, but only after you’ve manually followed the steps once. Luckily the community quickly responds and added a XrmToolBox plugin. There are however a lot of steps involved to publish and test your app inside a Dynamics environment. I do not have a lot of Node experience, but most of the commands are pretty self-explanetory. To install the tools and create the framework for my first component I followed the steps in this excellent blog post by Debajit Dutta. PowerApps Component Framework – IBAN Validator in action Installing PowerApps Component Framework I created an IBAN validator. This is validation we build for a lot of customers, so this is a good component to start with.Ĭurrently my solution uses deprecated code (the Xrm.Page object), so use with caution. Last but not least, this framework will come to canvas apps soon. ![]() It promises to provide us with the same API’s the Microsoft development team uses. No longer are we restricted by IFrame’s where we have little connection to the app. What excites me about this framework is that it provides developers with a native way to integrate development into Model-driven PowerApps / Dynamics 365 Customer Engagement. My first blog post is about my experience with the PowerApps Component Framework so far. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |