D365

https://roseahenry.blogspot.com/2018/09/download-implementing-microsoft.html
https://books.google.co.id/books?id=4JlGDwAAQBAJ&lpg=PP1&hl=id&pg=PP1&output=embed

What is Microsoft D365?

 Dynamics 365 is a Cloud based ERP & CRM Enterprise System.

 Dynamics 365 is the next step in the Evolution of a combined ERP & CRM Product.
 Dynamics 365 will be a starting place for organizations. It is unlikely that will fit your business perfectly
from day one. But once you start using it, Microsoft vision is that you will find the customizations you
need on Microsoft AppStore.

Solution – package – Model – project – element

 Cloud Hosted Environment , Browser based application.

 Visual Studio Development Environment.
 Over layering and Extension Development Concept.
 Layer Architecture.
 Model / Update model / Packages.
 Tables.
 Table Extension.
 Packages.
 Data Entities.
 Web Services.
 Power BI
 Life Cycle Services

Advantages of D365:

 Grate Storage on Azure & LCS (life Cycle Services)

 Customizable
 Mobile Access
 Online or On Premises
 .Net Development Integration

Life Cycle Services:

 Microsoft Azure-based administration and collaboration portal that facilitates application

lifecycle management.
 Data uploader, integrates with commonly used services such as Visual Studio Team Services
(VSTS)
 Supports multiple environments (i.e. Dev, QA, UAT, and Production).
 Support sure steps methodologies.
 Integrate with the TFS (Team Foundation Server).
 Application Lifecycle Management (ALM)

Power BI:

Power bi is a powerful analytical visualization for power users to quickly gain and insights into information over
cloud or on their premises. It works with Microsoft dynamics 365 to provide a self-service analytical solutions.
With power bi built directly into Dynamics 365, you gain access to powerful business intelligence. Real time on
any device no matter where you are in the world- with rich visuals, charts & graphics.
Power bi also has data warehouse capabilities including data preparation, data discovery, and
interactivity dashboards and can be embedded into azure cloud platforms.
Power apps:

Power apps is a mobile app with capabilities for power users with faster time to market delivery. It is the
foundation to build any web/mobile applications on top of Dynamics 365 solutions without writing any
significant of code.

Microsoft Dynamics Lifecycle Services (LCS):

Lifecycle Services (LCS) for Microsoft Dynamics is a cloud-based collaboration portal that customers and
their partners use to manage and assist with Microsoft Dynamics 365 for Finance and Operations
projects. From implementation to ongoing support and operations, LCS provides tools and resources that can
help guide the Dynamics 365 project to success. LCS is also the portal that is used to open support tickets
and communicate with the Microsoft Cloud Team. LCS and the Clients First portal allows ERP Project
Managers, IT Staff, and even the Project Team access to the project with any Internet device. The tools listed
below as part of LCS solution. The Clients First customer portal includes the project plan, budgets, hours
used, open tasks and tickets and invoices. In addition, your team can open support tickets through automated
email or within our portal.

Ask us about our Welcome Kit that outlines our portal, how to setup LCS, and includes the consulting teams
email addresses and cell phone numbers.

LCS implementation tools provided:

 Projects – Projects are the key organizer in LCS. Projects let you invite partners to collaborate with
you and they also let you track progress.
o When a project is created, it is based on an implementation methodology. You must follow the
methodology in your implementation project. The methodology framework is designed to guide
you through the implementation. As you perform actions in LCS, you can begin to mark the
phases and tasks as completed. Locked methodology tasks can be marked as completed after
you complete the prerequisite. You can click the lock icon to learn what you must complete
before you can mark a task as completed. As you work through the phases and tasks in the
methodology, environments become available for you to configure.
 Methodologies – Methodologies allow for tracking, communication and reporting on progress during
an implementation project. Microsoft provides a base methodology, Sure Step Agile, which provides the
following phases, includes the associated tasks and can be modified as needed or you can create your
own.
o Analysis
o Design and Develop
o Test
o Deploy
o Operate
 Business Process Modeler - Business process modeler lets you create, view, and modify standard
process flows. By using Business process modeler, you can achieve the following goals: standardize
process flows; align your business processes with industry-standard processes, as described by the
American Productivity & Quality Center (APQC); identify fit and gaps between user requirements and
the default functionality that Microsoft Dynamics products provides.
o You can use Business process modeler artifacts with the following applications:
  Microsoft Visual Studio Team Foundation Server (TFS) – You can generate a
consolidated list of gaps and import them manually into TFS as work items that include a
reference to the process flow.
 Microsoft Word – You can generate documentation for business processes.
 Microsoft Visio – You can export business process maps to Visio files.
 Task recordings - After you have created a BPM library, you'll need to use Task recorder to record
your processes and then upload them to the BPM library.
o Task recordings can be used for user training and control.
o Task recordings can also be used as test cases in Visual Studio Team Services (VSTS) projects.
This can serve as the basis for automated testing during development.
o Create user acceptance test libraries by using task recordings and BPM. The user acceptance
test libraries will allow you to create targeted test plans, manage the execution of tests and
investigate results.
o Task recordings can also be utilized to identify the security needs of users.
 Cloud-hosted environments - Cloud-hosted environments is a tool that you can use to deploy
Microsoft Dynamics environments on Microsoft Azure. When you use Cloud-hosted environments, you
must select the type of environment to deploy, such as a demo, developer/test, or production
environment. Based on your selection, the Cloud-hosted environments tool provisions the appropriate
number of virtual machines (VMs) in Azure. These VMs have Microsoft Dynamics components (and all
their prerequisites) already installed on them.

 Cloud-powered support - Cloud-powered support helps you manage support incidents. It lets you
create a VM in Azure that has the same hotfixes installed as your local environment. You can reproduce
and record an incident on the VM, and then submit the incident to our support team. Support follows up
by investigating and, if possible, testing a fix on the VM, and then sends the fix back to you for
verification.
 Configuration and data manager (preview) - Configuration and data manager (preview) lets you
copy a configuration from one instance to another. You can copy from and to environments that meet
the following criteria: they are managed as part of an LCS project; they run the Data Import/Export
Framework.
 Customization analysis - Customization analysis validates model files against best practices and
provides a report of potential areas for improvement.
 Issue search - Issue search helps you find existing solutions and workarounds for known issues in
Microsoft Dynamics products. You can see which issues have been fixed, which issues remain open, and
which issues have been resolved as “won’t fix.”
 License sizing estimator - License sizing estimator helps you estimate the number of licenses that
are required. It provides a shared workspace that lets you model default and customized roles, and
then automatically calculate the required client access licenses (CALs).
 System Diagnostics – System diagnostics helps administrators monitor Microsoft Dynamics
environments.
 Updates – The Updates page hosts the details about updates that are available for an environment.
 Upgrade Analysis - Upgrade analysis helps you plan your upgrade to the latest version of Microsoft
Dynamics 365 for Finance and Operations by analyzing code artifacts from Microsoft Dynamics AX 4.0,
Dynamics AX 2009, or Dynamics AX 2012.
 Usage Profiler - Usage profiler is a data-gathering tool that helps you describe your projected or
current usage to be used for various purposes, such as hardware sizing and support.
 Downloadable tools – The Downloadable tools page offers technical tools for data management,
security and development.
 Globalization portal – The globalization workspace provides localization services and information in a
single location. You can use search to access specific regulatory content and review recently submitted
alert information.
Microsoft Dynamics 365:

As shown in the image Modern work space combines office 365, Windows 10, and Enterprise Mobility &
Security System and it is offered as Microsoft 365. The Business Application category is a combination of
ERP & CRM business applications and is offered as Dynamics 365. The category is Cloud Application and
Infrastructure which provided by Azure. The last category Data & AI, deals with AI and Analytics.
Microsoft Dynamics is a unification of the current CRM and ERP Cloud solution into single Cloud Service.
Packages:

A Dynamics AX package is a deployment and compilation unit of one or more models. It includes model
metadata, binaries, cubes and other associated resources. One or more AX packages can be packaged into a
deployment package, which is the vehicle used for deployment on UAT and production environments. Packages
are packaged into a deployable package file for deployment to Sandbox or production environments.

Package can have one or more models.

Packages can have references to other packages, just like .NET assemblies can reference each other.

The new Dynamics AX is packages replaced the old AX 2012 model stores database.

A package folder contains a descriptor folder that lists all models belong to the package:

 Packages contain 1 or more models

 Packages can reference other packages
 Builds can be performed against 1 package or all packages

Model:
 A collection of elements (metadata/source files) that represent a distributable software solution.
 A visual studio project is not the same thing as a model. A project belongs to a model, and a model
may have several different projects.
 Models are a logical grouping of elements that relate to some specific solution.
 A model is not used to deploy customizations to a production environment, this would be a package.
 Metadata for models is stored locally in an xml file called Descriptor.XML.
 A Dynamics AX model is a group of elements that typically constitutes a distributable software
solution (including customizations of an existing solution). A model is a design-time concept. An
example of models: warehouse management model, a project accounting model …etc.

Model can have one or more projects.

Model may only belong to one package.

Models
 Created in Visual Studio
 Over-layer each other
 Metadata stored in Descriptor.XML file
 Primary system models
• Application Platform
• Application Foundation
• Application Suite

 A package is essentially a DLL file that contains one or more models.

 It’s a deployment unit.
 Packages could reference other packages in order to use elements from the models within the
referenced package.
 Package is equivalent to Ax 2012 model store.
 A package corresponds to its own mini-model store, with its own layers and models.
 Translates to a .NET assembly, meaning it's a unit of compilation (DLL).
 Split in smaller packages means smaller and faster compiles and smaller and faster deployments.
 References are not transitive and usually the package at a "higher" layer needs to reference some of
the lower layer packages as well.
 Content less DLL, fiches XML less resources.

Solution – package – Model – project – element

Creating Packages and models

This task can be achieved by following below steps:

From Visual Studio Go to Dynamics AX (menu) > Model Management > Create Model (wizard)

Under Add parameters tab complete the following:

Model name Enter the name of your new package as well as your new model
Model publisher Enter the name of the organization
Layer Choose the appropriate layer (Usually cus for customizations or var for value added
resellers)

Note: in previous AX versions we had to enter “license code” in order to access

specific layer, this is not required any more
Version The model version
Model description Some useful information about the new model
Model display name Defaulted to “Model name”, update model display name if you wish
Enter model parameters and click Next button

Under Select package tab you will be presented with 2 options:

Create new package Select this option if you are creating a new package. By default the name of this
package will be similar to model name entered in previous screen
Select existing package Select this option if you want to add the new model to an existing package. If
this option is enabled then you will need to select from the drop down menu

Select Create new package option and click Next button

Under Select referenced models select the existing models that you have the elements you will need to extend
in your new model

Click Next button

You will be presented with Summary tab. This tab will summarize what have been selected in previous tabs in
addition to 2 options:

Create new project Select this option to create a project to be added to current Visual Studio solution
Make this my default By default when you created a project it will be added under this new model
model for new
projects

Click Finish button

If you have checked off Create new project option, then you will be presented with New Project screen:

For the sake of this exercise we will select Dynamics AX7 project.

Congratulations you have created your first AX package, model and project in just few clicks!

Modifying Models

From Visual Studio Go to Dynamics AX (menu) > Model Management > Update model parameters (wizard)

Under Update model parameters tab select the following options:

Model name Select the model name you wish to modify

Model publisher Enter the name of the organization
Layer Disabled option
Version The model version
Model description Some useful information about the new model
Model display name Update model display name

Click Next button

Under Select referenced models select/deselect models

Click Next button

Under Summary tab, Click Finish button

Click Finish button

Layers

 Relevant (pertinent) for over-layering development approach

 Customizations in separate layers
 Irrelevant when using extensions
 Models over-layer each other
 Layer estuneproprietéd’un model pour résoudrele conflitentre model.