Feature Limitations of the Microsoft Dynamics NAV Web Client

Artigo
10/18/2021

Microsoft Dynamics NAV Web client supports most of the same Microsoft Dynamics NAV objects and features as Microsoft Dynamics NAV Windows client, but there are some small differences. This topic lists the features that are not supported or are partially supported by Microsoft Dynamics NAV Web client. These features are listed compared with the Microsoft Dynamics NAV Windows client. The topic is divided into the following sections:

General Features
Objects
Pages Features
Report Features
C/AL Triggers
C/AL Functions
User Interface Features

Note

In this topic, partially supported means that the feature does not have all the capabilities as it does in Microsoft Dynamics NAV Windows client or it works differently than in Microsoft Dynamics NAV Windows client.

General Features

The following table lists general features that are not fully supported by Microsoft Dynamics NAV Web client.

Feature	Level of support	Remarks
Chart parts	Not supported.	A chart part on a page is ignored in the Microsoft Dynamics NAV Web client and does not appear.
COM and Automation	Not supported.	If a Microsoft Dynamics NAV object implements Automation (objects and servers), then an error occurs when the object in run in Microsoft Dynamics NAV Web client.
Control add-ins	Not supported.	If a page that contains a control add-in is displayed in the Microsoft Dynamics NAV Web client, then the control add-in is ignored and nothing appears in its place.
Departments	Not supported.	The Departments button does not appear in the navigation pane of Role Center in the Microsoft Dynamics NAV Web client.
System Indicator	Not supported.	The Microsoft Dynamics NAV Web client always shows the name of the company that it connects to.
System parts that include Notes, MyNotes, and Record Links	Not supported.	A system part on a page is ignored by Microsoft Dynamics NAV Web client and does not appear.
Search	Partially supported.	Search is available from an action in the navigation pane of the Role Center window and on the General tab in a page's ribbon. Search can only find pages and reports, not views as with the Microsoft Dynamics NAV Windows client.
Microsoft .NET Framework Interoperability	Partially supported.	Microsoft .NET Framework interoperability objects that are configured to run on the client are not supported; objects that run on Microsoft Dynamics NAV Server are supported. For more information, see How to: Set .NET Framework Types to Run on the Microsoft Dynamics NAV Windows Client or Microsoft Dynamics NAV Server Computers.
Configuring the user interface for a profile	Partially supported.	You cannot perform the configuration in the Microsoft Dynamics NAV Web client. Instead, you use the Microsoft Dynamics NAV Windows client. For more information, see Configuring and Personalizing the Microsoft Dynamics Web Client.

Objects

The following object types are not supported by Microsoft Dynamics NAV Web client.

Feature	Level of support	Remarks
MenuSuite	Not supported.	MenuSuites are only used to build the Department page in the Microsoft Dynamics NAV Windows client.
XMLport	Partially supported.	Request pages are not supported. If you try to run an XMLport with a request page from the Microsoft Dynamics NAV Web client, then you receive an error that the XMLport page type is not supported. To run an XMLport without using a request page, you can set the UseRequestPage Property of the XMLport in XML Designer to No. Or, if the XMLport is run from C/AL code by calling the RUN Function (XMLport), then you can set the ReqWindow parameter to false.

MenuSuite

Not supported.

MenuSuites are only used to build the Department page in the Microsoft Dynamics NAV Windows client.

XMLport

Partially supported.

Request pages are not supported. If you try to run an XMLport with a request page from the Microsoft Dynamics NAV Web client, then you receive an error that the XMLport page type is not supported.

To run an XMLport without using a request page, you can set the UseRequestPage Property of the XMLport in XML Designer to No. Or, if the XMLport is run from C/AL code by calling the RUN Function (XMLport), then you can set the ReqWindow parameter to false.

Pages Features

This section includes page features that are not fully supported by Microsoft Dynamics NAV Web client.

General Page Features

The following page features are not fully supported by Microsoft Dynamics NAV Web client.

Feature	Level of support	Remarks
Navigate page type	Not supported.	If you try to open a page of the NavigatePage type in the Microsoft Dynamics NAV Web client, then an error occurs. Note If you have page that will display in the Microsoft Dynamics NAV Web client and the page includes an action that opens a page of the Navigate type, then you should consider removing or hiding the action. You can hide an action globally by setting the action's Visible Property to No. You can hide the action for a specific profile only by running the Microsoft Dynamics NAV Web client in the configuration mode, and then customizing the ribbon of the page. For more information, see How to: Configure a Role Center.
FixedLayout control for arranging page fields	Partially supported.	You can experience misalignment of captions and fields.
GridLayout control for arranging page fields	Partially supported.	The RowSpan and ColumnSpan properties on fields in the grid layout are not supported.

Page Properties

The following page properties are not supported or are partially supported by Microsoft Dynamics NAV Web client.

Note

Properties that are not supported are ignored by Microsoft Dynamics NAV Web client.

Control	Property	Level of support	Remarks
Page object	RefreshOnActivate	Not supported.
	PageType	Partially supported.	The NavigatePage option is not supported.
Group	FreezeColumnID	Not supported.
	ShowAsTree	Not supported.	Columns will be indented but they will not be expandable or collapsible.
	GroupType	Partially supported.	The FixedLayout and GridLayout options are not fully supported. With the FixedLayout option, you can experience misalignment of captions and fields. With the GridLayout option, the RowSpan and ColumnSpan properties on fields in the grid layout are not supported.
	IndentationControls	Partially supported.	Only supports indentation on one column. If you specify more than one column in the IndentationControls property, only the first column is used.
Field	ColumnSpan	Not supported.
	ControlAddin	Not supported.
	RowSpan	Not supported.
	Style	Not supported.
	StyleExpr	Not supported.
	AssistEdit	Partially supported.	The AssistEdit button does not appear on a field when a field or the page is in the view mode and never appears on a field that has the data type Option. You specify whether the field or page is in the view or edit mode by setting the Editable Property.
	DrillDown	Partially supported.	The property is not supported on repeater controls, which are typically used on List and ListPart type pages.
	DrillDownPageID	Partially supported.	The property is not supported on repeater controls, which are typically used on List and ListPart type pages.
	Importance	Partially supported.	The Additional option is not supported. Fields that are applied with the Additional option will always be hidden because there is no button for displaying more fields on the FastTab.
Part	ChartPartID	Not supported.	If a page contains a Chart part, then the part is ignored and nothing appears for the part in the Microsoft Dynamics NAV Web client.
	SystemPartID	Not supported.	If a page contains a System part, then the part is ignored and nothing appears for the part in the Microsoft Dynamics NAV Web client.
	PartType	Partially supported.	The System and Chart options are not supported. If a page contains a Chart part or System part, then the part is ignored and nothing appears for the part in the Microsoft Dynamics NAV Web client.

Report Features

The following table includes reports features that are not supported or are partially supported by Microsoft Dynamics NAV Web client.

Feature	Level of support	Remarks
Printing a report without using a request page by calling the Report.Run function	Partially supported.	If a report is run by calling the REPORT.RUN Function and the function call does not use a request page, then you must set up reports to print from Microsoft Dynamics NAV Server, otherwise you will get an error at runtime. Client-side printing is not supported in this scenario. For more information, see the following topics. How to: Specify Printer Selection for Reports STARTSESSION Function (Sessions) Printing Reports from a Background Session How to: Background Post with Job Queues
Filtering on request page of a report	Partially supported.	There is a limit on the number of filters a user can set. The user can only specify one filter in addition to the number of filter fields that are set by the ReqFilterFields property or the SETRECFILTER function in C/AL code.
Sorting on a report request page	Not supported.	Unlike the Microsoft Dynamics NAV Windows client, the sort action is not available.
Filter strings in a report URL	Not supported.	Unlike pages, you cannot filter a report by adding filter strings to the Internet address.
Document map in the report preview	Partially supported.	When you choose an item in the document map, the preview does not scroll to display the item. If the item is on another page, the preview scrolls to display the page but not to the specific item.

C/AL Triggers

This section lists the C/AL triggers that are not fully supported by Microsoft Dynamics NAV Web client. Triggers that are not supported are not invoked on an object at runtime.

Page Triggers

The following page triggers are not fully supported by Microsoft Dynamics NAV Web client.

Triggers	Level of support	Remarks
OnClosePage	Partially supported.	The OnClosePage trigger is invoked only when the Microsoft Dynamics NAV page is hosted in a modal popup dialog (MPO).
OnQueryClosePage	Partially supported.	The OnQueryClosePage trigger is invoked only when the Microsoft Dynamics NAV page is hosted in a modal popup dialog (MPO).

Field Control Triggers

The following field control triggers are not fully supported by Microsoft Dynamics NAV Web client.

Triggers	Level of support	Remarks
OnControlAddin	Not supported.
OnDrillDown	Partially supported.	The trigger is not invoked for fields in repeater controls on pages.
OnAssistEdit	Partially supported.	The trigger is not invoked when the field or page is in the view mode. You specify whether the field or page is in the view mode by setting the Editable Property.

C/AL Functions

This section lists the C/AL functions that are not supported by Microsoft Dynamics NAV Web client. Except when indicated otherwise, if you use a function that is not supported, you will receive an error at runtime.

Data type	Function	Level of support	Remarks
Automation	CREATE	Not supported.	If the C/AL code of Microsoft Dynamics NAV object calls the CREATE function, then an error occurs when the object is run in Microsoft Dynamics NAV Web client.
	ISCLEAR	Not supported.
Debugger	ACTIVATE	Not supported.	An error occurs at runtime.
Dialog	UPDATE	Not supported.	The function is ignored.
Report	REPORT.RUN	Partially supported.	If the ReqWindow parameter of the function is set to false, then you must set up reports to print from Microsoft Dynamics NAV Server, otherwise you will get an error at runtime. Client-side printing is not supported in this scenario. For more information, see How to: Specify Printer Selection for Reports and STARTSESSION Function (Sessions).
	REPORT.RUNMODAL	Partially supported.	If the ReqWindow parameter of the function is set to false, then you must set up reports to print from Microsoft Dynamics NAV Server, otherwise you will get an error at runtime. Client-side printing is not supported in this scenario. For more information, see How to: Specify Printer Selection for Reports and STARTSESSION Function (Sessions).
File	DOWNLOAD	Partially supported.	The DialogTitle, ToFolder, and ToFilter parameters are not supported. Not fully supported on devices that run on Apple IOS, such as iPad. You can only a download file when the iPad on which you are downloading the file has an application that supports the file type.
	DOWNLOADFROMSTREAM	Partially supported.	The DialogTitle, ToFolder, and ToFilter parameters are not supported. Not fully supported on devices that run on Apple IOS, such as iPad. You can only a download file if the device on which you are downloading the file has an application that supports the file type.
	UPLOAD	Partially supported.	The DialogTitle, FromFolder, and FromFile parameters are not supported. Not supported on devices that run on Apple IOS, such as iPad. When you try upload a file, the dialog box for uploading a file appears in the Microsoft Dynamics NAV Web client, but it is disabled and you cannot select a file.
	UPLOADINTOSTREAM	Partially supported.	The DialogTitle, FromFolder, and FromFile parameters are not supported. Not supported on devices that run on Apple IOS, such as iPad. When you try upload a file, the dialog box for uploading a file appears in the Microsoft Dynamics NAV Web client, but it is disabled and you cannot select a file.

User Interface Features

The following end-user interface features are not supported by Microsoft Dynamics NAV Web client.

Feature	Level of support	Remarks
Personalization	Partially supported.	Users cannot personalize the user interface directly from the Microsoft Dynamics NAV SharePoint client. Instead, they use the Microsoft Dynamics NAV Windows client to make the desired customizations. The changes appear the next time that they access the Microsoft Dynamics NAV Web client. For more information, see Configuring and Personalizing the Microsoft Dynamics Web Client.
Buffering of keyboard input for heads-down data entry	Not supported.
Select All feature in lists	Not supported.
Help	Partially supported.	Context-sensitive (F1) Help is not supported. There is a Microsoft Dynamics NAV Help action in the page ribbon, on the General tab, that targets a general Help source for the Microsoft Dynamics NAV Web client. You can change the Help target in the web.config file for the Microsoft Dynamics NAV Web client. For more information, see Configuring Microsoft Dynamics NAV Web Client by Modifying the Web.config File.
Advanced filtering on pages	Not supported.
Application menu	Not supported.
System Actions System actions are default actions in the Application menu and ribbon on pages and reports. System actions include the following: Copy Link to Page Recipient as Attachment Microsoft Word Microsoft Excel Print Page Set Work Date Select Language Select Server Select Company Customize Show as Chart Show as List OneNote Notes Links	Not supported.	The actions are not available in the user interface.
Actions related to a subpage in a part when the subpage is dynamically shown or hidden based on a user interaction	Partially supported.	The actions related to the subpage will always be present and active in the ribbon, even when the page is not shown. For an example, see page 5855 of the CRONUS International Ltd. demonstration database.
AssistEdit	Partially supported.	The AssistEdit button will not appear on a field if the field or the page is in the view mode (not editable).
Lookups	Partially supported.	The Up Arrow button will not appear on a field if the field or the page is in the view mode (not editable). Also, unlike the Microsoft Dynamics NAV Windows client, there is no advanced option in the lookup window for managing lookup items but there is filtering capability.
Drill down	Partially supported.	The property is not supported on fields in Repeater controls.
Filtering on request pages of reports	Partially supported.	There is a limit on the number of filters a user can set. The user can only specify one filter in addition to the number of filter fields that are set by the ReqFilterFields property.

Compartilhar via