Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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 Integrate Power Platform solutions to maximize the efficiency of your Finance & Operations projects

Arrow left icon
Product type Paperback
Published in Jan 2024
Publisher Packt
ISBN-13 9781801811590
Length 274 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Adrià Ariste Santacreu Adrià Ariste Santacreu
Author Profile Icon Adrià Ariste Santacreu
Adrià Ariste Santacreu
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: Dynamics 365 Finance and Operations and Power Platform FREE CHAPTER
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

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “OData actions are special methods executed on data entities that are decorated with the SysODataAction attribute.”

A block of code is set as follows:

Patch(
    'CustomersV3',
    LookUp('CustomersV3', 'Customer account' = CustomerGallery.Selected.'Customer account'),
    {
        'Credit limit': Value(CreditLimitInput.Text)
    }
);
Refresh(CustomersV3);
Set(CreditLimitValue, Value(CreditLimitInput.Text));

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

[SysODataAction('AASPostSalesOrder', false)]
    public static str postSalesorder(SalesId _salesId)
    {
        SalesFormLetter salesFormLetter;
        salesTable		salesTable;
        salesTable		= SalesTable::find(_salesId);
        salesFormLetter = SalesFormLetter::construct(DocumentStatus::Invoice);
        salesFormLetter.update(salesTable, DateTimeUtil::date (DateTimeUtil::applyTimeZoneOffset(DateTimeUtil::utcNow(), DateTimeUtil::getCompanyTimeZone())), SalesUpdate::All, AccountOrder::None, NoYes::No, NoYes::Yes);
        return CustInvoiceJour::findRecId(salesFormLetter.parmJournalRecord().RecId).InvoiceId;
    }

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “If we open the EntityKey node under Keys we see there’s only one field, the CustomerAccount one.”

Tips or important notes

Appear like this.

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 $19.99/month. Cancel anytime