Extending and Customizing Dynamics 365 FOR FINANCE AND OPERATIONS

Visual Studio

used to code , develop and extend functionalities in D365FO

we look how we could manage projects, models and build packages

then we will use Visual Studio to extend tables, forms and classes

we will explore the

AOT

Dynamics 365 menu

and the Solution Explorer and properties window

Azure DevOps

used to collaborate, plan, and also as Version Control tool

We will look how we can work with items tracking to get a grate traceability on projects

then we will use Azure DevOps to ship customisation across a variety of platforms

the application stack is a design time concept and it doesn't have anything with visual studio

it groups elements in folders so that they could be built separately

Application Platform

contains core of the business logic that d365 operates from

like Runtime and Data access

Application foundation

contains shared application elements

Like

Global address book

source document

application Suite

most of the functionalities that we create in Dynamics 365 for finance and operations are added as a reference to the Application Suite

model that contains all the business applications modules

like

HR

production

Finances

All these models are locked and cannot be changed

so customize the application

we first create a new model that reference the application suite

then we add new extension elements

we will be creating extension elements in Visual Studoi

we will customise metadata and source code

we will explore the customization of table, forms, report and security elements

and we will mention some currently supported extension based scenarios

then we will explore the extension of source code of table, forms and even class methods

to extend source code in Dynamics 365 for Finance and Operations we use one of the frameworks

Framework events

Chain of Command