Who this book is for

If you are a software developer new to Dynamics 365 Finance and Supply Chain Management programming or an experienced software engineer migrating from its predecessor, Dynamics AX, this book is an ideal tutorial to help you avoid the common pitfalls and make the most of this advanced technology. This book is also useful if you are a solution architect or technical consultant, as it provides a deeper insight into the technology behind the solution.

In order to gain access to Microsoft Dynamics 365 for Operations, you need to be either a Microsoft partner or a Microsoft customer. To sign up for access as a partner, you can refer to Lifecycle Services (LCS) for Finance and Operations apps partners at https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/lifecycle-services/getting-started-lcs.

To sign up for a subscription as a customer, refer to Lifecycle Services (LCS) for Finance and Operations apps customers at https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/lcs-works-lcs.

You will need to download or deploy a Dynamics 365 Finance and Supply Chain Management development virtual machine (VM) in Azure. To run the VM locally, you will need at least 100 GB free space available and a minimum of 12 GB free memory, ideally 24 GB. It can run on as little as 8 GB of assigned memory, but the performance would suffer as a result.

The official system requirements are as follows:

• System requirements (https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/get-started/system-requirements )
• Development system requirements (https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/dev-tools/development-system-requirements)

If you are using the digital version of this book, we advise you to type the code yourself or access the code via the GitHub repository (link available in the next section). Doing so will help you avoid any potential errors related to the copying and pasting of code.

Download the example code files

You can download the example code files for this book from your account at www.packt.com. If you purchased this book elsewhere, you can visit www.packtpub.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packt.com.
2. Select the Support tab.
3. Click on Code Downloads.
4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Extending-Microsoft-Dynamics-365-Finance-and-Supply-Chain-Management-Cookbook-Second-Edition. In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

Conventions used

There are a number of text conventions used throughout this book.

CodeInText: 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: "If we wanted to create an extension of the WHSLoadTable table, it would call the WHSLoadTable.extension object by default."

A block of code is set as follows:

public Name StandardCarrierName()
{
    return 'Ziriqi'; 
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

public static ConVMSVehicleTable Find(ConVMSVehicleId _vehicleId, boolean _forUpdate = false)
{
    ConVMSVehicleTable vehicle;
    vehicle.selectForUdate(_forUpdate);
    select firstonly * from vehicle where vehicle.VehicleId == _vehicleId;
    return vehicle;
}

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Right-click on 59 in the Solution Explorer and choose Properties."

Warnings or important notes appear like this.

Tips and tricks appear like this.