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

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.