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

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.