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

Questions

Here are some questions to test your understanding of the chapter. The answers to the questions are given at the end.

  1. What tool in Microsoft Power Automate is used to post an adaptive card to a Teams channel or chat?
    1. Post a text card and wait for a response
    2. Post adaptive card and wait for a response
    3. Post adaptive card and do not wait for a response
    4. None of the above
  2. In the described approval workflow, what happens if no response is given within the 15-minute timeout?
    1. The process automatically approves the request
    2. The process automatically rejects the request
    3. A timeout notification is sent to the user with a link to the record needing approval
    4. The workflow stops and needs to be restarted
  3. What is the purpose of creating a parallel branch in this approval workflow?
    1. To manage the response from Teams and to process a timeout
    2. To send multiple adaptive cards to different users
    3. To duplicate the workflow for backup
    4. To process both approval and rejection simultaneously
  4. How...