Death of Classic (C/SIDE) Client
Yesterday, during a coffee break at the What’s New in Microsoft Dynamics NAV 2009 Technical for Application Consultants training in Vilnius, Lithuania (a fabulous place, by the way), a discussion arose around the destiny of the Classic (or C/SIDE) client in NAV. Some participants stated that “it’s never going to go away” because “Microsoft would not dare shutting it down”.
Unfortunately, it is going away, and quickly. Maybe it wasn’t too obvious at first, because Microsoft never actually said explicitly that “Classic client is going to be discontinued”, but if you read the latest Statement of Direction for Microsoft Dynamics NAV, it’s there.
I am one of those people who only use keyboard with NAV. Classic, of course. Seriously, I can keyboard my way through NAV and do literally everything—and I am dead serious about the everything part of it—with only my keyboard. With Classic, mouse is quietly resting under piles of papers. In RTC, mouse is an active animal.
RoleTailored client for Microsoft Dynamics NAV 2009 was one of those things for me that looked really nice in presentations, but in real-life, I didn’t see much value there. It looked good from far, but far from good. I would dare saying it saw more runtime at conferences and presentations than in real life. For partners, it was difficult to sell it. With new customers, okay, there were considerable chances the RTC would convince them. With old customers, you were been better-off not showing it at all.
We old dogs really have to learn new tricks with RTC (RoleTailored Client), as I found out couple of days ago. A customer of mine asked me for a quick report. I don’t typically do reports, but I thought—“not a big deal, it’s just a report”—so I fixed it, tested it, made sure it worked, then deployed it to production.
Microsoft Dynamics NAV Classic client has some features which are simply unbeatable when it comes to productivity and speed, one of them being primary-key filtering. When you set a single-value filter on primary key fields in a table, and then insert a new record in the same table, primary key fields are automatically populated with values from the filter.