Skip to main content

NAV 2015 - Cumulative Update 11 Released.

Hi all,

Please find below the details of  Cumulative Update 11 released for Microsoft Dynamics NAV 2015.

Title - Cumulative Update 11 for Microsoft Dynamics NAV 2015

Build No. - 42603

Release Date - Sep, 2015

Local Version Included - AU, AT, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, RU, SE, UK.

Download Link

Note: Implementing this cumulative update will require a database conversion unless you have already implemented cumulative update rollup 9.

Platform Issues Resolved in the Cumulative Update are -

OData crashes the service tier if a field uses a dynamic ShowMandatory property.
The development environment appears blurred on high-DPI displays.
The installer fails when you install the IIS-URL-Rewrite-Module.
Some tenant operations do not work in Windows.
You notice that the ConflictTarget folder is empty after Merge-NAVApplicationObject has reported documentation conflicts.
If you change a value that is used in the CaptionClass functionality, the change is not reflected until you restart the client.
"Standard Day/Time Unit is not valid property for Field" warning when you try to use the Join-NAVApplicationObjectFile cmdlet in PowerShell.
The service tier crashes when the next Odata page is called.
The Web service calls return misleading status.
"Object reference not set to an instance of an object" error message when you export data to a *.navdata file if the middle tier is configured with the Services Option Format value set to OptionString.
After you enter a user ID in the To field, you cannot create a note with a blank user until the page is reopened.
The @Change Log Setup (Table) filter is not valid for the Name field on the Object table. A '('"error occurs when you use the EVALUATE function.
A note for a purchase order cannot be opened from the Purchase Orders list page.
Add-in files are not copied to the client from the server when the version is changed.
The Update-NavApplicationObject PowerShell commandlet fails in Windows 10.
"Server page is not open" error message when you close a page.
The Export to Excel function does not respect the HideValue property.
The client crashes when you use the RUNMODAL function.
The client crashes with NEXTDATE.
The development environment hangs in Windows 10 when coming out of hibernation or sleep.
Scrolling in the development environment does not work properly in Windows 10.
Editable notes are inconsistent.
The Web client and the Windows client show the same characters differently.
"A call to <xxx> failed with this message: Could not load file or assembly '<yyy>, Version=<vvv>, Culture=neutral, PublicKeyToken=<kkk>' or one of its dependencies" error message after you install cumulative update 10.
Scrolling in lists does not work in the Chrome browser on Android.

For information about previous Update Rollup / Cumulative update released for Microsoft Dynamics NAV 2013, NAV 2013 R2 & NAV 2015 please Navigate to Hotfix Label or follow the Link.

All These links required valid Partner Source / Customer Source Login...

Saurav Dhyani


Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.