Small changes that makes a big difference seems to be the slogan for NAV2017.
One of these small changes that have been asked for a long time is to make it easier for partners to upgrade their customers by allowing us to add/remove fields and objects within the Microsoft number ranges which are 1..49999.
This has been a restriction for three decades.
I spend a lot of my time in SQL Server Management Studio. I rarely ever run tables anymore from Object Desingner and run most of my data conversions directly in T-SQL.
Why? Because it is so much faster, I can script things, save and restore scripts, share accross customers etc.
One of the pain points of working with SQL Server Queries has Always been the full companyname in front of the real table name. For this reason Intellisense was more or less useless for NAV databases.
This is fixed in SSMS 2016!
When you type
select * from Custom
SQL Server Management Studio will show this
How cool is that!
You can download SSMS 2016 for free here
By Marije Brummel, product specialist at ForNAV
When one of my customers asked me to upgrade them from NAV 2009 R2 classic to NAV 2016, I was convinced that we would do all the reports with RDLC. For two reasons:
The project started mid-2015 and at that time RDLC was the only option. I had done several other upgrades from classic to role tailored using RDLC reports with the help of external resources.
Marije Brummel Blog | Business Central, Azure and more...