Skip to main content
Dynamics 365
·
1 min read

Client Add-in can fail with communication error (HTTP 413) in the Microsoft Dynamics NAV 2015 Web Client

Based on a very interesting development request about a drag-and-drop Client Add-In targeted for both Windows and Web clients for Dynamics NAV, we have been able to identify a communication error with Microsoft Dynamics NAV 2015 when users select and upload multiple files using a client add-in in the Dynamics NAV Web client.

You might have heard about this through MVP blogs such as http://vjeko.com/blog/drag-and-drop-file-upload-for-microsoft-dynamics-nav-2013-r2.

The issue is related to the fact that callback service requests has been limited to the WCF default message size (48 Kb). This turns out to be a problem for all partners who develop custom Client Add-Ins that send a discrete amount of data. 

How to resolve this issue with Microsoft Dynamics NAV 2015:

  1. Update MaxReceivedMessageSize on WCF binding to a suitable value as described in an earlier blog post. 
    This value is taken from system.web/httpRuntime maxRequestLength (the default value should be 4 Mb).

  2. Download and deploy – at the very least the platform files – CU 10 for Microsoft Dynamics NAV 2015 (Build No. 42222) or a later CU in order to let the platform files update the WCF message size as indicated in bullet point #1.

Please note that this feature was enhanced in Microsoft Dynamics NAV 2015 while earlier versions still stick with the WCF default message size and limitation.

 

These postings are provided “AS IS” with no warranties and confer no rights. You assume all risk for your use.

 

Duilio Tacconi                                      Microsoft Dynamics Italy         

Microsoft Customer Service and Support (CSS) EMEA

Special thanks to Lukasz Zoglowek from Microsoft Dynamics NAV Development Team and Kris Jordaens from sde.be 

navteam

Related posts