Reader small image

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

Product typeBook
Published inJan 2024
PublisherPackt
ISBN-139781801811590
Edition1st Edition
Right arrow
Author (1)
Adrià Ariste Santacreu
Adrià Ariste Santacreu
author image
Adrià Ariste Santacreu

Adrià Ariste Santacreu has been working in the Microsoft business applications' field since 2010, starting with Axapta and Microsoft Dynamics AX, and since 2016 with Microsoft Dynamics 365 F&O. A technical solution architect and developer who loves solving requirements with all the tools available in the Microsoft ecosystem, like the Power Platform or Azure services that can be used with Finance and Operations. Adrià has been recognized as a Microsoft MVP since 2020 in the Business Applications category thanks to his community contributions, like speaking at events and conferences and writing technical articles about Dynamics 365 F&O, Azure, Dataverse, and the Power Platform.
Read more about Adrià Ariste Santacreu

Right arrow

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 page is locked
Previous PageNext Page
You have been reading a chapter from
Extending Dynamics 365 Finance and Operations Apps with Power Platform
Published in: Jan 2024Publisher: PacktISBN-13: 9781801811590

Author (1)

author image
Adrià Ariste Santacreu

Adrià Ariste Santacreu has been working in the Microsoft business applications' field since 2010, starting with Axapta and Microsoft Dynamics AX, and since 2016 with Microsoft Dynamics 365 F&O. A technical solution architect and developer who loves solving requirements with all the tools available in the Microsoft ecosystem, like the Power Platform or Azure services that can be used with Finance and Operations. Adrià has been recognized as a Microsoft MVP since 2020 in the Business Applications category thanks to his community contributions, like speaking at events and conferences and writing technical articles about Dynamics 365 F&O, Azure, Dataverse, and the Power Platform.
Read more about Adrià Ariste Santacreu