Skip to main content

#msdyn365bc 2022 Release Wave 2 - See the primary key for table fields in IntelliSense.

Hi Readers,

In this series we are discussing what's new in Business Central 2022 (Wave 2) a.k.a BC21.

This article we will discuss about - See the primary key for table fields in IntelliSense.

With this series we will understand what's new the product and learn it.

Hope you like the series, please add comments to article.

#msdyn365bc #2022RW2

Business Value - 

When you work with table fields in code, it's important to know if the fields are primary key members, as well as the sequence of the fields in the primary key. To provide contextual information, and avoid tedious steps on navigating to table definitions, primary key members are now marked with a (PKx) in the IntelliSense list, where x is a sequential number that indicates the order of the field in the key.

Feature details - 

  • The information makes it easier to identify the table fields that make up the primary key as well as the sequency of these fields in the key.

  • While working on Extension Development, it's hard to remember sequence of fields while doing a Setrange and Get Statement. For Some tables its easier but it adds an additional step to check the table Primary Key Fields. 

  • With this new feature IntelliSense will highlight fields with PK(x) where x is the order of fields as part of primary key.

Sample Sales Header Primary Key Fields

As Sales Header has two fields in Primary key - Document Type and No., those fields are highlighted as PK1 & PK2.


Sample Invt. Posting Buffer Primary Key Fields

Inv. Posting Buffer has multiple fields in primary key. There are 09 fields in the primary key of table. These fields are highlighted from PK1 to PK9.


  

What Would have been great?

  • If Primary key fields are listed on top of intelliSense, that would have been great to find these fields during coding.
  • If top of table in intelliSense, if PK1 to PKx fields are listed that will be great for developers.

For other articles related to What's New in Business Central 21, refer here.

Hope you learn and will be able to utilize this feature as Business Central 21 is available.  

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 searchi...

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.