I read on Wikipedia that Visual Studio supports code completion since 1996. Roughly the same period that Navision came with the development environment that we still have to use.
Personally I loved this environment when it had the capability of running forms. You could make your own tools that ran on the same spot as where you were developing. Being a guy that hates to do repetitive tasks I made a lot of tools. Most of these tools are included in Object Manager today.
With the version of NAV2013 forms are no longer supported and therefore the development environment cannot run the tools we all made. With the lack of running these tools the development environment is IMHO not acceptable as a development environment. After doing one RTC project I stopped with the RTC and wend back doing only 2009 projects waiting for a better development environment.
Waiting for a couple of years now and being afraid that Microsoft have other priorities I thought why not build our own Development Environment? And Navgate was born!
In the following weeks we will reveal more and more functionalities of Navgate. We already uploaded a PowerPoint to Mibuso last week. And being downloaded over 500 times already, I am starting to believe that I am not the only one that wants a better developing experience! :)
Please look at the following movie at YouTube for a sneak preview of Navgate for Object Manager.
If you want to see Navgate in live action you can get a demo at the IDYN booth at Directions or NAV TechDays.
Time for a sneak preview of OMA9.
Did you ever realize that with the upcoming NAV2013 RTC it is probably more difficult for an end user to import a FOB. New users are not used to work with the Classic Client. It would be better if he could import the FOB with the RTC. Or the Web Client, when he is e.g. working at home on a tablet.
This is possible with the new Object Manager which we will demo at the NAV TechDays. See you in Antwerp!
Look at this demo on YouTube!
Oh my! Do I like this new feature of OMA8.5!
In previous versions of the OMA you had to wait like 10 seconds if you opened a part of the OMA that needed up to date where used data. Doing that all day long it was pretty frustrating some times. This is no longer needed. The OMA now installs an SQL trigger that will check the where used data in 100ms. A logic consequence is that the question "Do you want to update the where used objects?" is also no longer needed and therefore made optional in the OMA setup.
Go to the "Administration Tasks" and execute "Add Ask SQL trigger".
Set the "Update Where Used" to "Always" if you like.
This trick has nothing to do with the OMA but I really want to share it. Did you ever had to search for a COMMIT? The command CONSISTENT can help you with that.
This command is specially build to make sure that at the end of a transaction the G/L Accounts are in balance. In codeunit "Gen. Jnl.-Post Line" you will see the following C/AL statement:
(BalanceCheckAmount = 0) AND (BalanceCheckAmount2 = 0) AND
(BalanceCheckAddCurrAmount = 0) AND (BalanceCheckAddCurrAmount2 = 0));
If you put a COMMIT somewhere is the posting routine after the consistency of the "General Ledger Entry" was set to false you will get the following beautiful error:
So if you have to find a COMMIT someday the only thing you have to do is first set a random table to CONSISTENT(FALSE) and the debugger will bring you to the first COMMIT.
PS: Kudos goes to rmv_RU. This topic was the first time I read about this.
I just read in the blog of Luc van Vugt that the development environment of NAV will be transferred to the RTC.
I think this is great news. The way we have to develop in NAV2013 where the testing and tooling is in the RTC and the developing is done separately in the dev-env is almost unacceptable. Try to run a table and you'll have to wait 10 seconds till it opens.
I'm very happy that Microsoft is going to put these two worlds back together again. Let's keep our fingers crossed that we can develop with the same speed in the 'new' environment as we did in NAV2009. Or even better, that the 'new' environment is just a copy of the current environment. Chances are big it will!!
For the OMA this is also great news. It will just sit and wait in the RTC and wait till everything gets back together like one big happy family.