Skip to main content

MSDYN365BC - Futuristic CAL Development - What is allowed and What is Not?

Hi Readers,

As discussed in the Last article, in this post we will discuss with What we can and cannot do to think Futuristic development and then continue with our Customer Requirements.

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

We cannot Modify, Change, Delete & comment any standard part in any object, but we can add new in few base objects.

Read detailed of what limited modified we should do in Base Objects so that our code is Future Ready.

As we seen in the previous article where we modified 1 Base table and 1 Base Page. Let's try to understand What is allowed and not allowed for Future.

What we cannot change, modify & delete in Standard Microsoft Tables -

  • Any properties for any existing standard Field.
  • Any properties for any existing Standard key.
  • Any existing Global & Local variables, Global & Local Text Contacts.
  • Any existing Local & Global Function.
  • Any code in Table Trigger and Standard Field Triggers.
  • Any in Field Groups.

What we can do in Standard Microsoft Tables - 

  • Add New Field in Table.
  • Add Code in New Field Triggers.
  • Add New Key. (Only with Custom Field Added in Table, No Base Field).
  • Add New Local & Global Function.

What we cannot change, modify & delete in Standard Microsoft  Pages - 

  • Any properties of any Existing standard Field.
  • Any properties of any existing Standard Factbox.
  • Any properties of any Existing Standard Group.
  • Any properties of any Existing standard Action.
  • Any properties of any Existing Global & Local variables, Global & Local Text Contacts.
  • Any existing Local & Global Function.
  • Any code in Page Trigger and Standard Page Field Triggers.

What we can do in  Standard Microsoft  Pages - 

  • Add New Field in Page.
  • Add Code in New Page Field Trigger.
  • Add New Factbox in Page.
  • Add New Group in Page.
  • Add New Page Action.
  • Add New Local & Global Function.
I think a haven't missed anything on the above list but to summarize all. Anything written in any Base Microsoft Object from Microsoft we should consider it Locked. We are not allowed to change any of base code. 

Limited modification allowed in tables and pages objects is what listed above. All other objects should not be modified. 

Standard Report, Codeunit, Query, Xmlport and MenuSuite should not be modified and that is what Future Require from us as Developers. 

Next article, we will discuss What possibility Microsoft added to add custom code in Base Objects. Let me know if you have any specific question as the comment to this article, I will try to cover it in Future articles.

Stay Tuned for More!

Regards,
Saurav Dhyani

Comments

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 - 

Dynamics 365 Business Central 2021 release wave 2 (BC19) Released.

Hi Readers, As we all were expecting Microsoft have Released Business Central 2021 Release Wave 2 Today a.k.a BC19. In this article we will see what all is announced with the General Availability.  Starting Today Customers & Partners can start using Business Central 19. #msdyn365bc #bc19

Error After Restore SQL Backup of NAV 2013 Database

Hi all, we are facing a conman issue during restoring a SQL Database backup restored for NAV 2013. While Trying to run object from Object Designer we get below listed error (even the service is configured properly) - --------------------------- Microsoft Dynamics NAV Development Environment --------------------------- There are no NAV Server instances available for this database. You must ensure that a NAV Server instance is running and is configured to use the database before you perform this activity. --------------------------- OK    ---------------------------