Limitations of ClickOnce Installed on the Microsoft Dynamics NAV Windows Client

The following are limitations of ClickOnce installed on the Microsoft Dynamics NAV Windows client.

Command-line arguments - ClickOnce installed on the Microsoft Dynamics NAV client cannot be run with custom command-line arguments. For example, this affects the following scenarios:

• An end user cannot specify the Home page.
• An end user cannot specify a profile. He can only use his default profile.
• An end user cannot disable personalization. An administrator can disable personalization on a profile.
• An administrator cannot configure profiles. He should use the MSI-installed client for this task.
• An end user cannot run in full-screen mode.
• An end user cannot disable the navigation pane.

Hyperlinks - The protocol handler dynamicsnav:// is not registered during ClickOnce installation, which means that the Microsoft Dynamics NAV client cannot be activated by choosing a hyperlink. This could impact the following scenarios:

• End users cannot send each other links to specific pages.
• An end user cannot use the link on a OneNote page.
• An end user cannot use the link on a report.
• The debugger cannot be started.

External components calling the Microsoft Dynamics NAV Windows client - A ClickOnce-installed Microsoft Dynamics NAV Windows client will be installed in a randomly generated folder, and when it is upgraded to a new version, it will be installed a new randomly generated folder. This means that external components will not be able to detect where the Microsoft Dynamics NAV Windows client executable is located. This could impact the following scenarios:

• An end user can send a list page to Excel, but cannot refresh data from the Excel application.
• Third-party applications cannot start the Microsoft Dynamics NAV Windows client.

How to show more than 999+ in RTC Cue

Issue: If we have more than 999 Sales Orders – Open then the RTC cue will show 999+ instead of exact number.

Solution: 

1.    Go to particular activities page. (SO Processor Activities in my case)

2.    Select the field which is having issue (<Sales Orders - Open>)

3.    Click Properties from View or shortcut Shift + F4

4.    Select property Image

5.    Now it is set to <Stack>

6.    Change it to None

7.    Save the page and restart the RTC

Style Sheet Tool for Microsoft Dynamics NAV2013

The Style Sheet Tool for Microsoft Dynamics NAV2013 is available in Mibuso Downloads Section.
http://mibuso.com/dlinfo.asp?FileID=1543

The Style Sheet Tool for Microsoft Dynamics NAV2013 enhances the Style Sheet feature in Microsoft Dynamics NAV 2013 by allowing you to easily and without programming knowledge create and modify style sheets in Microsoft Office Word.

Changes to Style Sheet tool for NAV 2013.

1.Multi-multiline support is added, so it is now possible to add several multiline records to the style sheet. Note though that records can not be indented, but added sequentially.

2.Setup page is modified to add Open/Save/Send options.

3.In NAV 2009, codeunit 50000 was released for automatic integration of the Style Sheet functionality with pages. Pages were then exported in xml format and modified by running codeunit 50000, to add style sheet actions.

This no longer works for NAV2013, as export /import of objects in xml format is no longer an option. Hence, adding Style Sheet Action (button) to each page must be done manually.

Follow the example below when adding the style sheet action to a page:

i. Add the action to the action designer (under appropriate group) with following properties:

Expanded Type SubType Name Caption
0 Action <Action680> Style Sheets

ii. OnAction trigger should contain following line:

StyleSheetDataMgt.LoadStylesheetDataRTC(GETPOSITION,CURRENTKEY,PAGE::"");

where StyleSheetDataMgt is a variable of type codeunit, 682 (Style Sheet Data Management).