Hello,
With NAV 2013, the Classic Client and the Native Navision database were discontinued.
Keys
In the Native database the structure how Navision maintained Keys was perceived as revolutionary and a main part in the success of the Application and its architecture.
Within a Key one could specify SumIndexFields. These are decimals that then would be totalled in the background without writing code.
Everything in NAV like G/L, Inventory and Jobs is based on that principle. You will not find any Application code in NAV that totals entries.
To be able to sort something a Key was required in the Native database. A maximum of 40 keys were allowed. This is different in SQL Server.
SQL Server can sort without having an Index (the name for Key in SQL Server). Therefore with the Native database being discontinued the possibility opened to change the Key story in NAV.
Therefore with the introduction of NAV 2013 R2 it is no longer required to define a Key on a table to sort data.
It is now possible to sort on any column in the UI.
And it is also possible to sort on any field from AL code.
SetCurrentKey no longer requires a Key to be created in the table.
With NAV 2013, the Classic Client and the Native Navision database were discontinued.
Keys
In the Native database the structure how Navision maintained Keys was perceived as revolutionary and a main part in the success of the Application and its architecture.
Within a Key one could specify SumIndexFields. These are decimals that then would be totalled in the background without writing code.
Everything in NAV like G/L, Inventory and Jobs is based on that principle. You will not find any Application code in NAV that totals entries.
To be able to sort something a Key was required in the Native database. A maximum of 40 keys were allowed. This is different in SQL Server.
SQL Server can sort without having an Index (the name for Key in SQL Server). Therefore with the Native database being discontinued the possibility opened to change the Key story in NAV.
Therefore with the introduction of NAV 2013 R2 it is no longer required to define a Key on a table to sort data.
It is now possible to sort on any column in the UI.
And it is also possible to sort on any field from AL code.
SetCurrentKey no longer requires a Key to be created in the table.
No comments:
Post a Comment