Skip to main content

MSDYN365BC - Futuristic CAL Development - Tables and Fields.

Hi Readers,

Are you Ready to start re-learn how to customize NAV?

If you are new to this then Please Refer Table of Index.

In this article, we will start working on the requirement and will also discuss What is allowed and what is not if you have to code in C/AL.


Below are some guidelines for Futuristic Development in CAL based on NAV Version - 

  • Pre NAV 2016 - Upgrade to Latest version or Use Hooks. Refer to Latest version Code to identify Events added by Microsoft and use them as HOOKS.
  • NAV 2016 to NAV 2018 - Use Events and Refer to Latest version Code to identify New Events added by Microsoft and use them as HOOKS.
  • Business Central on-Prem - Update to latest version.

** Latest Version - Latest cumulative Update for Business Central on-Prem (Released Monthly).

I will be using Microsoft Dynamics 365 Business Central (on-Prem) CU03 for this article series. Let's try to complete customer requirements.

Add a New table to have customer store Expense Code and Description.
I am using Table ID 50000 and Table Name Expense as shown below with Primary Key Code.



Add a New Page for the new table created. As per requirement, we will require the List Page.
I am using Page ID 50000 and Page Name Expenses as shown below.



Add a new field in Table 15 G/L Account, Field ID - 50000 and set Table Relation to new Table Created as shown below.



Add new field added in G/L Account table to Page 17 G/L Account Card in General Tab as shown below.



I know this was pretty simple to follow. In the next article, we will see what we can and cannot do in things discussed in this article.
  1. New Table.
  2. New Page.
  3. Modify Base Table.
  4. Modify Base Pages.

Stay connected and Learn Futuristic CAL Development with us.

Your comments are welcome.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Post a Comment

Popular posts from this blog

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.

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.