NAV 2015 development environment annoyance

rjsf

Is it still possible to run objects directly off of the object designer the way it used to be prior to NAV2015? Now the RTC fires up whenever I want to do something as mundane as browse a table. It is too time consuming now.

Rob_Hansen

Nope. It's a brave new world. Well...not that new. Since NAV 2013.

jglathe

Leave the RTC open, it's faster then. But not as fast as we were used to... By far.

lvanvugt

This was also the case with 2013 (and R2) as the Development Environment (C/SIDE) is no code run time any more. All code is executed by the Service Tier.

Rikt-It

In ServiceTierAdministator (download at Mibuso) it's possibly.

kriki

[Merged some posts from http://www.mibuso.com/forum/viewtopic.php?t=64490 to this topic.]

mdPartnerNL

Rikt-It wrote:

In ServiceTierAdministator (download at Mibuso) it's possibly.

Haven't seen an option to run a table? Have a screenshot?

rjsf

jglathe wrote:

Leave the RTC open, it's faster then. But not as fast as we were used to... By far.

Thanks, but that doesn't help, because NAV would open another Role Center instance for every new object I run regardless. So for example, I run the "Tracking Specification" table, NAV will open 2 windows in succession - the Role Center and the table view. Then I run the "Reservation Entry" table, NAV will yet again open another 2 windows - another Role Center instance and the table view. It fills up my taskbar very quickly. Why does it open a new Role Center instance everytime? Is there a way to change that behavior? It is just so cumbersome now, I can't imagine this as an improvement.

DenSter

It's not supposed to start a new role center, assuming you are still in the same database. As long as you have a role center instance running, each table that you run should start within the context of the same role center.

Something is not right if you get a new one each time you run a table, although I don't know what is wrong.

Capone

I have discovered that often when it opens up a new RTC it is usually because the first RTC is waiting for user input or is locked in a certain window mode (Zooming).

Otherwise you can create your own table viewer in RTC by making a listpage on the virtual table object.
Add an action that has the following code:

CASE Type OF
  Type::Page : PAGE.RUN(ID);
  Type::Codeunit : CODEUNIT.RUN(ID);
  Type::Report : REPORT.RUN(ID);
  Type::XMLport : XMLPORT.RUN(ID);
  Type::Table : HYPERLINK(GETURL(CLIENTTYPE::Current,COMPANYNAME,OBJECTTYPE::Table,ID));  //Tip from Gunnar (?)
  Type::Query : HYPERLINK(GETURL(CLIENTTYPE::Current,COMPANYNAME,OBJECTTYPE::Query,ID));
END;

However, this doesn't work on ClickOnce clients.