Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Extending Dynamics 365 Finance and Operations Apps with Power Platform

You're reading from  Extending Dynamics 365 Finance and Operations Apps with Power Platform

Product type Book
Published in Jan 2024
Publisher Packt
ISBN-13 9781801811590
Pages 274 pages
Edition 1st Edition
Languages
Author (1):
Adrià Ariste Santacreu Adrià Ariste Santacreu
Profile icon Adrià Ariste Santacreu
Toc

Table of Contents (18) Chapters close

Preface 1. Part 1: Dynamics 365 Finance and Operations and Power Platform
2. Chapter 1: Dynamics 365 F&O and Low-Code Development 3. Chapter 2: Dual-Write and Virtual Tables 4. Part 2: Extending Dynamics 365 F&O with Power Platform
5. Chapter 3: Power Automate Flows in Dynamics 365 6. Chapter 4: Replacing F&O Processes with Power Automate 7. Chapter 5: Building Automations and Integrations 8. Chapter 6: Power Apps: What’s in it for Finance and Operations Consultants? 9. Chapter 7: Extending F&O Apps with Power Apps 10. Chapter 8: Power BI Reporting for Dynamics 365 F&O Apps 11. Part 3: Adding AI to Your Flows and Apps
12. Chapter 9: Integrating AI Builder 13. Part 4: Dataverse and Power Platform ALM
14. Chapter 10: Environment Management 15. Chapter 11: Solution Management 16. Index 17. Other Books You May Enjoy

Using OData actions

In the next step, we’ll call an OData action to validate whether the workflow step can be completed. OData actions are special methods executed on data entities that are decorated with the SysODataAction attribute. For example, the validate method looks as follows:

[SysODataAction('validate', false), Hookable(false)]
public static boolean validate(WorkflowWorkItemInstanceId WorkflowWorkItemInstanceId)

We can see that the method takes one parameter. When calling the action from Postman, for example, we need to include the parameters in the JSON body of the request. To do it in Power Automate, we can use the Execute action action of the F&O connector (see Figure 4.5):

Figure 4.5 – Using the execute action

Figure 4.5 – Using the execute action

When you select the OData action, the Power Automate action will update its UI and you will see a new field for each parameter that the action you’ve selected has. In the case of the validate action...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $19.99/month. Cancel anytime}