NAV 2009 RTC MenuSuite and Action pane itmes relation

Let's talk about how smart RTC is when designing action menu items (Home items).

When designing Menu action (Home items) You want Your users to have on-eye ability to use most user NAV funcionalities. So naturally You'll add actions that represent those form (or card) NAV items.
NAV RTC has programmed logic that sounds something like this:


When designing action cues use those drop down forms as home items because it is big probability that user will use those forms often!


In short this means that all forms or cards used when developing cues those forms will automatically show in home items and you don't need to manually add them on Page actions.

Of course there is a little bit problem if you want to remove those items from home acitons. This is still RTC built in funciontality and it is depended on Microsoft's will to make this RTC modification.

NAV 2009 RTC Blank MenuSuite Items

When creating / converting menusuites from Classic client to RTC client there is one thing, besides menu structure and permissions, that You need to think about and that is multilanguage options.

RTC handles multilanguage items drastically harder than classic client. This means that you must specify menusuite item captions for every item and for evey language used. If You don't populate Caption ML those itmes won't show in RTC departmets for language that wasn't specified on seperate items.

Of course Your items will show when viewing RTC using default language.

RTC vs Classic MenuSuite

In the Classic client, accessing forms and reports is done from the navigation pane, which displays menus that are contained in a MenuSuite object. In the RTC client, navigation to pages and reports is done with:

• Role Centers
• Departments

MenuSuite object that is useed in the Classic client can be transofmed to a Departments page that is used in the RoleTailored client.
The Departments page contains entire suite of functionality available to the company. In this way, the Departments page in the RTC is similar to the navigation pane in the Classic client. The Departments page is also a MenuSuite object with layered item structure but is designed specifically for RTC.
When creating a new MenuSuite object, you must select either the Classic client or the RoleTailored client as the target.

The ID of a MenuSuite object for the RTC will be the Classic client ID plus 1000, as shown in the following table.

MenuSuite object in the Classic client	MenuSuite object in the RoleTailored client
10 MBS	1010 Dept - MBS
51 Add-on 1	1051 Dept - Add-on 1

MenuSuite object is transformed by using the Transformation Input File (TIF) Editor. The MenuSuite transformation creates a suggestion for a Departments page that is based on the navigation pane, transformation rules, and input.
After MenuSuite object transform ation, you must verify whether you need to make additional updates to the transformed Departments page. The RoleTailored client has different functionality and different user experience (UX) requirements than the navigation pane in the Classic client. The additional updates that you make to the transformed Departments page can take advantage of the new functionality.
To reduce the number of these manual updates that you have to make after transformation, verify that you meet the following conditions before transforming a MenuSuite object.

Condition	Reason
PageType is assigned to all form objects.	Form objects will be placed in a Department Category based on PageType.
CardFormID is assigned to all list form objects with a card.	Card Form IDs in MenuSuite will be replaced with the related list.
Microsoft Dynamics NAV Developer Toolkit is installed to provide data about which reports are ProcessingOnly reports.	ProcessingOnly reports are placed in the Tasks category on department pages. Other reports are placed in the Reports and Analysis category on department pages.