Book Image

Extending Dynamics 365 Finance and Operations Apps with Power Platform

By : Adrià Ariste Santacreu
Book Image

Extending Dynamics 365 Finance and Operations Apps with Power Platform

By: Adrià Ariste Santacreu

Overview of this book

Uncover the synergy between Microsoft Power Platform and its integration with Dynamics 365 Finance & Operations (F&O) with this essential guide to implementing low-code and no-code concepts to not only extend and enhance F&O but also improve maintainability and speed up development. Systematically exploring Power Platform, this book covers topics such as Dataverse, Power Automate, Power Apps, and Power BI using real-world scenarios in Dynamics 365 F&O to offer practical insights. You’ll then master the integration of F&O and Power Platform using dual-write and virtual tables, and delve into process automation with Power Automate. The book further deepens your proficiency in Power Apps by showing you how they can be used to extend the F&O functionality and incorporate artificial intelligence using AI Builder and its pre-trained AI models ready to use with your data. Throughout, you’ll gain a solid understanding of the diverse components of Power Platform and how they can transform your Dynamics 365 F&O experience. By the end of this book, you’ll be equipped with the skills and knowledge necessary to fully harness the immense potential of Power Platform and Dynamics 365 F&O.
Table of Contents (18 chapters)
Free Chapter
1
Part 1: Dynamics 365 Finance and Operations and Power Platform
4
Part 2: Extending Dynamics 365 F&O with Power Platform
11
Part 3: Adding AI to Your Flows and Apps
13
Part 4: Dataverse and Power Platform ALM

Loading and modifying F&O data into a Power App

As we saw when we learned about Power Automate flows, we can use the standard F&O connector or the native Dataverse connector using F&O virtual tables in Dataverse. When working with Power Apps, we can also choose between the standard F&O connector and the native Dataverse connector, if we have virtual tables enabled for our F&O environment.

Once again, using one or the other is a decision you and your team should take before you start building anything. Both connectors will fulfill the requirements and work fine.

In the following sections, we’ll learn what’s wrong (in my opinion) with the native F&O connector, and why I prefer to use the Dataverse connector. Don’t get me wrong, there’s nothing wrong with the F&O connector, but Dataverse prefers Dataverse.

Using the F&O standard connector in a canvas app

Let’s learn how to create a canvas app using the F&amp...