Cumulative Update 5 for Microsoft Dynamics NAV 2015 has been released

Cumulative Update 5 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015. 

The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

•   AU - Australia
•   AT - Austria
•   BE - Belgium
•   CH – Switzerland
•   CZ – Czech Republic
•   DE - Germany
•   DK - Denmark
•   ES - Spain
•   FI  - Finland
•   FR - France
•   IS - Iceland
•   IT - Italy
•   NA - North America
•   NL - Netherlands
•   NO - Norway
•   NZ - New Zealand
•   RU – Russia
•   SE - Sweden
•   UK - United Kingdom
• 
  

Note: You must convert the database if you are upgrading to Cumulative Update 5 from a cumulative update earlier than Cumulative Update 4 (build 39663). For more information, see Converting a Database in Help for Microsoft Dynamics NAV. 

You can download the cumulative update from KB 3039824  – Cumulative Update 5 for Microsoft Dynamics NAV 2015 (Build 40262). 

Upgrading Reports from NAV2013,NAV2013R2 to NAV2015

If you want to use reports from earlier versions of Microsoft Dynamics NAV, you must upgrade the reports before you can run or modify them. The report formats that were supported in Microsoft Dynamics NAV 2013 were client report definition (RDLC) 2008. In Microsoft Dynamics NAV 2013 R2, the report formats are replaced with client report definition (RDLC) 2010.

Typically, upgrading reports is part of upgrading the Microsoft Dynamics NAV application. However, you can also import reports from .txt files or .fob files.

Importing RDLC 2008 Reports

If you import reports that have RDLC 2008 format from Microsoft Dynamics NAV 2013, then you must upgrade the reports to Microsoft Dynamics NAV 2013 R2.

Upgrading reports is part of the Upgrading the Application Code section of the upgrade process. Follow steps 1 through 5d in the Identifying Customized Objects topic to begin the upgrade process. Then export the relevant report objects, and import them into Microsoft Dynamics NAV 2013 R2.

The following illustration shows the upgrade process for the reports.

When you import the report, Microsoft Dynamics NAV automatically upgrades it to RDLC 2010. SQL Server Report Builder first validates that the reports have the correct RDLC 2008 format and then upgrades them to RDLC 2010 format.

In Object Designer, when the upgrade is complete, the Modified flag is set to Yes. All other properties for the report are not changed.

After the upgrade, you can open the layout in Visual Studio. For more information, see How to: Integrate Report Dataset Designer and Visual Studio Report Designer. You must compile the imported report before you can run it.

Importing RDLC 2010 Reports

You can import reports that have RDLC 2010 format to Microsoft Dynamics NAV 2013 R2. Upgrading the reports is an automated process. SQL Server Report Builder first validates that the reports have the correct RDLC 2010 format and then imports them.

In Object Designer, no properties for the report are changed.

Note : You cannot import reports from versions earlier than Microsoft Dynamics NAV 2013 into Microsoft Dynamics NAV 2013 R2. If you want to import a Microsoft Dynamics NAV 2009 report, you must first upgrade the report to Microsoft Dynamics NAV 2013, and then import it into Microsoft Dynamics NAV 2013 R2

How can I Reset the page Number for each group in rdlc reports

Please follow the below steps to get the page n of m for each page

Step 1:  Make sure there's a textbox in the report which contains the group expression

Step 2:  Add shared variables to track the current group and page offset

 Shared offset as Integer
 Shared currentgroup as Object

Step 3:  Add a custom function to set the shared variables and retrieve the group page number

 Public Function GetGroupPageNumber(group as Object, pagenumber as Integer) as Object
  If Not (group = currentgroup)
   offset = pagenumber - 1
   currentgroup = group
  End If
  Return pagenumber - offset
 End Function

Step 4: Use the function in the page header or footer

 =Code.GetGroupPageNumber(ReportItems!Category.Value,Globals!PageNumber)

Note:  Because this uses static variables, if two people run the report at the exact same moment, there's a slim chance one will smash the other's variable state  (In SQL 2000, this could occasionally happen due to two users paginating through the same report at the same time, not just due to exactly simultaneous executions)  If you need to be 100% certain to avoid this, you can make each of the shared variables a hash table based on user ID (Globals!UserID).