Mixed RTC and Classic client access

faniba

Hello,

can we mix to two access mode in same time, i mean can we have some users accessing database with classic and others with rtc client.

is there a possiblity or any issue about that.

thank for help !

cernst

No problem you can use classic and RTC at the same time.

JDVyska

Bear in mind that if the RTC users want to use Notes & Notifications, only other RTC users will see those.

Reports will also look a little different depending on who prints them, as the formatting is a little different.

MChilari

If you are doing any modifications then you have to do the changes to Forms and Pages. Same thing goes with the Reports, you have to do the changes in Classic Format and also in RTC Layout. If you are creating any import/export processes then you have to use XML Ports for RTC Client.

You also need to train People in two different versions of the System.

It would be nice to use either Classic or RTC.

Thanks

jlandeen

Depending on client requirements one mixed mode option I've worked with is to use the classic client for internal users and then web interfaces and web services for external users. All web users are using the new Service Tier.

This can also be a good model for older installations that would like web access but are happy with their current functionality - if you upgrade the executables to NAV 2009 then you can have the best of both worlds without going thorugh a full upgrade.

Alex_Chow

No issues technically.

But functionally you'll get some problems as people will expect "basic" features in RTC to be in Classic and vice versa. What people end up doing is have RTC and classic open at the same time, thus consuming more user licenses than normal.

jlandeen

Yeah that's a whole other isseue of RTC versus Classic. Hopefully they can improve the RTC experience enough by version 7 so that clients don't have to be forced to decide.

Sog

jlandeen wrote:

Yeah that's a whole other isseue of RTC versus Classic. Hopefully they can improve the RTC experience enough by version 7 so that clients don't have to be forced to decide.

I heard that the classic client won't be available in 7

JDVyska

1) Statement of Direction:
https://mbs.microsoft.com/customersourc ... d?r=18&l=6

or if you don't have a partner login:
viewtopic.php?f=16&t=40000

Upgrade your "I've heard" to "I've read"


2) Forms will be discontinued. There's discussion if that means that Classic will still exist, but Pages will run in it, or if the old Forms will still work, just not be supported.

jlandeen

One of my big concerns is the workflow and rich functionaly that is available through the Forms object is not currently present in the Pages object. Will we get a WYSIWUG type editor for Pages? Will the caching and page load up be improved? Debugging and testing in the RTC is currently very difficult and we're back to screen dumps and confirm/message boxes!

Those problems with the current RTC lead to additional development time which leads to additional cost for a client and there may not add value.

A risk with going classic client is that you are telling customers they are not on the latest version of the UI and they will have to have some upgrade to get to future functionality that will be painful (i.e. form to page upgrade) at some point down the line.

I don't think it is an easy choice as there are pros and cons to RTC and Classic. The one nice thing a mixed mode may give you is that some users who are comfortable with RTC can move to it while others who are not (or have Form functionality they need) can stay on classic a little while longer.

Alex_Chow

There are so many usuability issues with RTC... The best first step for Microsoft to address this is to replicate usability feature in the classic client into RTC (including searching on lines in header/line forms, case sensitive searching).

The users can wait 1 more second for pages to load up if screen is really worth it.

JDVyska

Alex Chow wrote:

The best first step for Microsoft to address this is to replicate usability feature in the classic client into RTC (including searching on lines in header/line forms, case sensitive searching).

You mean your users aren't fans of having to type "@*james*|@*jim*|@*jack*" in filters? Jeez...

(Agreeing, and grumbling, with you.)