Skip to main content

MSDYN365BC - Customer Requirement for AL Development Blog Series.

Hi Readers,

As promised in the last article we will start building our first extension using VS Code and AL Programming Language.

This is the first article in this series where we will take the example of a customer requirement and going forward we will develop that using VS Code as our first Extension for Microsoft Dynamics 365 Business Central. I am considering this example as this capture all object types and also include base object changes.

Customer Requirement - 
  1. Customer Requires to track Source of Sales. 
  2. The Design that customer requires, a table where they can list down the Code and Description of Source of Sales. They should be able to disable any Source of Sales.
  3. They should be able to key in those details in that table using a page. 
  4. The user should be able to select the Source of sales in Sales documents and its a mandatory field to key in before posting a sales document.
  5. Source of sales should be available in Item Ledger Entries & posted sales doc. for analysis.
  6. Customer may ask for a report based on Source of Sales.

Pre-requisites - 
I am sure that you have completed all the pre-requisites before you start working on these customizations, below is the list of pre-requisites that need to be completed -

This article also acts as Table of contents for all articles related to this blog series - 
Hope you find this useful. Let me know your thoughts on the same.

Be Ready for development in AL and learn with me!

Saurav Dhyani


Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.