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.