Book Image

Extending Microsoft Dynamics 365 for Operations Cookbook

By : Simon Buxton
Book Image

Extending Microsoft Dynamics 365 for Operations Cookbook

By: Simon Buxton

Overview of this book

Dynamics 365 for Operations is the ERP element of Microsoft’s new Dynamics 365 Enterprise Edition. Operations delivers the infrastructure to allow businesses to achieve growth and make better decisions using scalable and contemporary ERP system tools. This book provides a collection of “recipes” to instruct you on how to create—and extend—a real-world solution using Operations. All key aspects of the new release are covered, and insights into the development language, structure, and tools are discussed in detail. New concepts and patterns that are pivotal to elegant solution designs are introduced and explained, and readers will learn how to extend various aspects of the system to enhance both the usability and capabilities of Operations. Together, this gives the reader important context regarding the new concepts and the confidence to reuse in their own solution designs. This “cookbook” provides the ingredients and methods needed to maximize the efficiency of your business management using the latest in ERP software—Dynamics 365 for Operations.

Related Content you might be interested in

Current Title:

Small book image
Extending Microsoft Dynamics 365 for Operations Cookbook
Simon Buxton
May, 2017 | 442 pages
Small book image
Dynamics 365 for Finance and Operations Development Cookbook
Abhimanyu Singh | Deepak Agarwal
Aug, 2017 | 480 pages
Small book image
Implementing Microsoft Dynamics 365 for Finance and Operations
Rahul Mohta | Yogesh Kasat | Jila Jeet Yadav
Sep, 2017 | 562 pages
Small book image
Implementing Microsoft Dynamics 365 for Finance and Operations Apps
Rahul Mohta | Yogesh Kasat | Jila Jeet Yadav | Sandeep Shukla
Mar, 2020 | 528 pages
Table of Contents (16 chapters)
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Sections
Conventions
Reader feedback
Customer support
Free Chapter
1
Starting a New Project
Starting a New Project
Introduction
Creating the Visual Studio Team Services project
Connecting Visual Studio to Visual Studio Team Services
Creating a new Model and Packages
Configuring project and build options
Creating a Label file
2
Data Structures
Data Structures
Introduction
Creating enumerated types
Creating extended data types
Creating setup tables
Creating a parameter table
Creating main data tables
Creating order header tables
Creating order line tables
3
Creating the User Interface
Creating the User Interface
Introduction
Creating the menu structure
Creating a parameter form
Creating menu items
Creating setup forms
Creating details master (main table) forms
Creating a details transaction (order entry) form
Creating form parts
Create tiles with counters for the workspace
Creating a workspace
4
Application Extensibility, Form Code-Behind, and Frameworks
Application Extensibility, Form Code-Behind, and Frameworks
Introduction
Creating a handler class using the Application Extension factory
Hooking up a number sequence
Creating a create dialog for details transaction forms
Creating a SysOperation process
Adding an interface to the SysOperation framework
5
Business Intelligence
Business Intelligence
Introduction
Creating aggregate dimensions
Creating aggregate measures
Creating aggregate data entities
Creating and using key performance indicators
6
Security
Security
Introduction
Creating privileges
Creating duties
Creating security roles
Creating policies
7
Leveraging Extensibility
Leveraging Extensibility
Introduction
Extending standard tables without customization footprint
Creating data-event handler methods
How to customize a document layout without an over-layer
Creating event handler methods
Extending standard forms without customization footprint
Using a form event handler to replace a lookup
Creating your own query functions
8
Data Management, OData, and Office
Data Management, OData, and Office
Introduction
Creating a data entity
Extending standard data entities
Importing data through Data Import/Export Framework
Reading, writing, and updating data through OData
9
Consuming and Exposing Services
Consuming and Exposing Services
Introduction
Creating a service
Consuming a Dynamics 365 for Operations SOAP service
Consuming a Dynamics 365 for Operations JSON service
Consuming an external service within Dynamics 365 for Operations
10
Extensibility Through Metadata and Data Date-Effectiveness
Extensibility Through Metadata and Data Date-Effectiveness
Introduction
Using metadata for data access
Using Interfaces for extensibility through metadata
Making data date-effective
11
Unit Testing
Unit Testing
Introduction
Creating a Form Adaptor project
Creating a Unit Test project
Creating a Unit Test case for code
Creating a test case from a task recording
12
Automated Build Management
Automated Build Management
Introduction
Creating a Team Services Build Agent Queue
Setting up a build server
Managing build operations
Releasing a build to User Acceptance Testing
13
Servicing Your Environment
Servicing Your Environment
Introduction
Applying metadata fixes
Applying binary updates
Servicing the build server
Servicing the Sandbox - Standard Acceptance Test environment
14
Workflow Development
Workflow Development
Introduction
Creating a workflow type
Creating a workflow approval
Creating a manual workflow task
Hooking up a workflow to the user interface
Creating a sample workflow design
15
State Machines
State Machines
Introduction
Creating a state machine
Creating a state machine handler class
Using menu items to control a state machine
Hooking up the state machine to a workflow

Introduction

Unit testing helps ensure that the code both fulfills the requirement, and future changes (even in other packages) do not cause a regression. The unit test is written as a separate package that references the package it is testing. If we follow Test Driven Development (TDD), we will write the tests early in the process (some would argue first). TDD changes the way we think when writing code. Should we need to make a change to a project, we are forced to update the test case code (as the tests will otherwise fail)--this promotes a test-centric approach to development, and naturally reduces the test cycles. Regression in other packages is caught by the build process; the build server will download all checked-in code, perform a build, and then look for tests to execute. Any tests that fail are reported and the build--depending on the build's set up--will be marked as failed.

Each partner or customer...

Previous Section
End of Section 2
Next Section